Re: [PATCH] cx18: Fix a sleep-in-atomic bug in snd_cx18_pcm_hw_free

Hi Jia-Ju, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.12-rc3 next-20170531] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/cx18-Fix-a-sleep

Re: [PATCH] cx18: Fix a sleep-in-atomic bug in snd_cx18_pcm_hw_free

Hi Jia-Ju, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.12-rc3 next-20170531] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/cx18-Fix-a-sleep

Re: [PATCH] ivtv: Fix a sleep-in-atomic bug in snd_ivtv_pcm_hw_free

Hi Jia-Ju, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.12-rc3 next-20170531] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/ivtv-Fix-a-sleep

Re: [PATCH] ivtv: Fix a sleep-in-atomic bug in snd_ivtv_pcm_hw_free

Hi Jia-Ju, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.12-rc3 next-20170531] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/ivtv-Fix-a-sleep

[RFC PATCH 02/10] objtool, x86: add several functions and files to the objtool whitelist

In preparation for an objtool rewrite which will have broader checks, whitelist functions and files which cause problems because they do unusual things with the stack. These whitelists serve as a TODO list for which functions and files don't yet have undwarf unwinder coverage. Eventually most of

[RFC PATCH 02/10] objtool, x86: add several functions and files to the objtool whitelist

In preparation for an objtool rewrite which will have broader checks, whitelist functions and files which cause problems because they do unusual things with the stack. These whitelists serve as a TODO list for which functions and files don't yet have undwarf unwinder coverage. Eventually most of

[RFC PATCH 04/10] objtool: add undwarf debuginfo generation

Now that objtool knows the states of all registers on the stack for each instruction, it's straightforward to generate debuginfo for an unwinder to use. Instead of generating DWARF, generate a new format called undwarf, which is more suitable for an in-kernel unwinder. See

[RFC PATCH 03/10] objtool: stack validation 2.0

This is a major rewrite of objtool. Instead of only tracking frame pointer changes, it now tracks all stack-related operations, including all register saves/restores. In addition to making stack validation more robust, this also paves the way for undwarf generation. Signed-off-by: Josh

[RFC PATCH 04/10] objtool: add undwarf debuginfo generation

Now that objtool knows the states of all registers on the stack for each instruction, it's straightforward to generate debuginfo for an unwinder to use. Instead of generating DWARF, generate a new format called undwarf, which is more suitable for an in-kernel unwinder. See

[RFC PATCH 03/10] objtool: stack validation 2.0

This is a major rewrite of objtool. Instead of only tracking frame pointer changes, it now tracks all stack-related operations, including all register saves/restores. In addition to making stack validation more robust, this also paves the way for undwarf generation. Signed-off-by: Josh

[RFC PATCH 05/10] objtool, x86: add facility for asm code to provide CFI hints

Some asm (and inline asm) code does special things to the stack which objtool can't understand. (Nor can GCC or GNU assembler, for that matter.) In such cases we need a facility for the code to provide annotations, so the unwinder can unwind through it. This provides such a facility, in the

[RFC PATCH 06/10] x86/entry: add CFI hint undwarf annotations

Add CFI hint undwarf annotations to entry_64.S. This will enable the undwarf unwinder to unwind through any location in the entry code including syscalls, interrupts, and exceptions. Signed-off-by: Josh Poimboeuf --- arch/x86/entry/Makefile | 1 -

[RFC PATCH 05/10] objtool, x86: add facility for asm code to provide CFI hints

Some asm (and inline asm) code does special things to the stack which objtool can't understand. (Nor can GCC or GNU assembler, for that matter.) In such cases we need a facility for the code to provide annotations, so the unwinder can unwind through it. This provides such a facility, in the

[RFC PATCH 06/10] x86/entry: add CFI hint undwarf annotations

Add CFI hint undwarf annotations to entry_64.S. This will enable the undwarf unwinder to unwind through any location in the entry code including syscalls, interrupts, and exceptions. Signed-off-by: Josh Poimboeuf --- arch/x86/entry/Makefile | 1 - arch/x86/entry/calling.h | 5 +

[RFC PATCH 10/10] x86/unwind: add undwarf unwinder

Add a new 'undwarf' unwinder which is enabled by CONFIG_UNDWARF_UNWINDER. It plugs into the existing x86 unwinder framework. It relies on objtool to generate the needed .undwarf section. For more details on why undwarf is used instead of DWARF, see tools/objtool/Documentation/undwarf.txt.

[RFC PATCH 10/10] x86/unwind: add undwarf unwinder

Add a new 'undwarf' unwinder which is enabled by CONFIG_UNDWARF_UNWINDER. It plugs into the existing x86 unwinder framework. It relies on objtool to generate the needed .undwarf section. For more details on why undwarf is used instead of DWARF, see tools/objtool/Documentation/undwarf.txt.

[RFC PATCH 09/10] extable: add undwarf table sorting ability to sorttable script

The undwarf table needs to be sorted at vmlinux link time, just like the extable. Extend sorttable's functionality to do so. Signed-off-by: Josh Poimboeuf --- init/Kconfig| 4 ++ scripts/Makefile| 2 +- scripts/link-vmlinux.sh | 7 +-

[RFC PATCH 09/10] extable: add undwarf table sorting ability to sorttable script

The undwarf table needs to be sorted at vmlinux link time, just like the extable. Extend sorttable's functionality to do so. Signed-off-by: Josh Poimboeuf --- init/Kconfig| 4 ++ scripts/Makefile| 2 +- scripts/link-vmlinux.sh | 7 +- scripts/sorttable.c | 178

[RFC PATCH 07/10] x86/asm: add CFI hint annotations to sync_core()

This enables the unwinder to grok the iret in the middle of a C function. Signed-off-by: Josh Poimboeuf --- arch/x86/include/asm/processor.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h index

[RFC PATCH 08/10] extable: rename 'sortextable' script to 'sorttable'

Soon it will be used to sort the undwarf table as well. Signed-off-by: Josh Poimboeuf --- Documentation/dontdiff | 2 +- scripts/.gitignore | 2 +- scripts/Makefile | 4 ++-- scripts/link-vmlinux.sh|

[RFC PATCH 07/10] x86/asm: add CFI hint annotations to sync_core()

This enables the unwinder to grok the iret in the middle of a C function. Signed-off-by: Josh Poimboeuf --- arch/x86/include/asm/processor.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h index 3cada99..9b90129 100644

[RFC PATCH 08/10] extable: rename 'sortextable' script to 'sorttable'

Soon it will be used to sort the undwarf table as well. Signed-off-by: Josh Poimboeuf --- Documentation/dontdiff | 2 +- scripts/.gitignore | 2 +- scripts/Makefile | 4 ++-- scripts/link-vmlinux.sh| 2 +-

[RFC PATCH 00/10] x86: undwarf unwinder

Create a new 'undwarf' unwinder, enabled by CONFIG_UNDWARF_UNWINDER, and plug it into the x86 unwinder framework. Objtool is used to generate the undwarf debuginfo. The undwarf debuginfo format is basically a simplified version of DWARF CFI. More details below. The unwinder works well in my

[RFC PATCH 01/10] objtool: move checking code to check.c

In preparation for the new 'objtool undwarf generate' command, which will rely on 'objtool check', move the checking code from builtin-check.c to check.c where it can be used by other commands. Signed-off-by: Josh Poimboeuf --- tools/objtool/Build|

[RFC PATCH 00/10] x86: undwarf unwinder

Create a new 'undwarf' unwinder, enabled by CONFIG_UNDWARF_UNWINDER, and plug it into the x86 unwinder framework. Objtool is used to generate the undwarf debuginfo. The undwarf debuginfo format is basically a simplified version of DWARF CFI. More details below. The unwinder works well in my

[RFC PATCH 01/10] objtool: move checking code to check.c

In preparation for the new 'objtool undwarf generate' command, which will rely on 'objtool check', move the checking code from builtin-check.c to check.c where it can be used by other commands. Signed-off-by: Josh Poimboeuf --- tools/objtool/Build|1 +

Re: [PATCH v3 14/23] scsi: hisi_sas: add v3 cq interrupt handler

> + case SAS_PROTOCOL_SSP: > + { > + unsigned char op = task->ssp_task.cmd->cmnd[0]; > + > + if (op == READ_6 || op == WRITE_6 || > + op == READ_10 || op == WRITE_10 || > + op == READ_12 || op == WRITE_12 || > +

Re: [PATCH v3 14/23] scsi: hisi_sas: add v3 cq interrupt handler

> + case SAS_PROTOCOL_SSP: > + { > + unsigned char op = task->ssp_task.cmd->cmnd[0]; > + > + if (op == READ_6 || op == WRITE_6 || > + op == READ_10 || op == WRITE_10 || > + op == READ_12 || op == WRITE_12 || > +

Re: [PATCH v3 13/23] scsi: hisi_sas: add phy up/down/bcast and channel ISR

On Wed, May 31, 2017 at 10:33:05PM +0800, John Garry wrote: > From: Xiang Chen > > Add code to initialise interrupts and add some interrupt handlers. > > Signed-off-by: John Garry > Signed-off-by: Xiang Chen > --- >

Re: [PATCH v3 13/23] scsi: hisi_sas: add phy up/down/bcast and channel ISR

On Wed, May 31, 2017 at 10:33:05PM +0800, John Garry wrote: > From: Xiang Chen > > Add code to initialise interrupts and add some interrupt handlers. > > Signed-off-by: John Garry > Signed-off-by: Xiang Chen > --- > drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 281 >

RE: [PATCH v2] net: fec: add post PHY reset delay DT property

From: Florian Fainelli Sent: Thursday, June 01, 2017 9:53 AM >To: Andy Duan ; Rob Herring ; >Quentin Schulz >Cc: mark.rutl...@arm.com; net...@vger.kernel.org; >devicet...@vger.kernel.org;

RE: [PATCH v2] net: fec: add post PHY reset delay DT property

From: Florian Fainelli Sent: Thursday, June 01, 2017 9:53 AM >To: Andy Duan ; Rob Herring ; >Quentin Schulz >Cc: mark.rutl...@arm.com; net...@vger.kernel.org; >devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; >thomas.petazz...@free-electrons.com >Subject: Re: [PATCH v2] net: fec: add

linux-next: Tree for Jun 1

Hi all, Changes since 20170531: The net-next tree gained a conflict against the net tree. The mfd tree still had its build failure so I used the version from next-20170530. The drivers-x86 tree lost its build failure. The target-bva tree gained a conflict against the target-updates tree

linux-next: Tree for Jun 1

Hi all, Changes since 20170531: The net-next tree gained a conflict against the net tree. The mfd tree still had its build failure so I used the version from next-20170530. The drivers-x86 tree lost its build failure. The target-bva tree gained a conflict against the target-updates tree

[LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process

Hi, In debian wheezy system while writing logs to SSD using tee command , we are experiencing kernel hung problem. Can anyone help in avoiding this problem ? I haven't subscribed to kernel mailing list,so re-ponders please CC me in the reply. Kernel trace : kernel: [ 960.964830] INFO: task

[LINUX-KERNEL] Kernel hung for more than 120 seconds due to tee process

Hi, In debian wheezy system while writing logs to SSD using tee command , we are experiencing kernel hung problem. Can anyone help in avoiding this problem ? I haven't subscribed to kernel mailing list,so re-ponders please CC me in the reply. Kernel trace : kernel: [ 960.964830] INFO: task

Re: [Linux-graphics-maintainer] No mouse cursor since 36cc79bc9077319c04bd3b132edcacaa9a0d9f2b

> m...@ox.io hat am 11. Mai 2017 um 07:38 geschrieben: > > > > > Sinclair Yeh hat am 10. Mai 2017 um 18:46 geschrieben: > > > > > > Hi, > > Hi, > > > On Wed, May 10, 2017 at 12:31:39PM +0200, m.t wrote: > > > > > > > Thomas Hellstrom hat am 10. Mai 2017 um 10:35 geschrieben: > > > > > >

Re: [Linux-graphics-maintainer] No mouse cursor since 36cc79bc9077319c04bd3b132edcacaa9a0d9f2b

> m...@ox.io hat am 11. Mai 2017 um 07:38 geschrieben: > > > > > Sinclair Yeh hat am 10. Mai 2017 um 18:46 geschrieben: > > > > > > Hi, > > Hi, > > > On Wed, May 10, 2017 at 12:31:39PM +0200, m.t wrote: > > > > > > > Thomas Hellstrom hat am 10. Mai 2017 um 10:35 geschrieben: > > > > > >

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

On Wed, 31 May 2017 19:07:15 -0500 Larry Finger wrote: > On 05/31/2017 10:32 AM, Michael Büsch wrote: > > On Wed, 31 May 2017 13:26:43 +0300 > > Kalle Valo wrote: > > > >> Jia-Ju Bai writes: > >> > >>> The driver may

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

On Wed, 31 May 2017 19:07:15 -0500 Larry Finger wrote: > On 05/31/2017 10:32 AM, Michael Büsch wrote: > > On Wed, 31 May 2017 13:26:43 +0300 > > Kalle Valo wrote: > > > >> Jia-Ju Bai writes: > >> > >>> The driver may sleep under a spin lock, and the function call path is: > >>>

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

On Thu, 01 Jun 2017 07:27:20 +0300 Kalle Valo wrote: > Michael Büsch writes: > > >> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c > >> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c > >> > @@ -2859,7 +2859,9 @@ static void

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

On Thu, 01 Jun 2017 07:27:20 +0300 Kalle Valo wrote: > Michael Büsch writes: > > >> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c > >> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c > >> > @@ -2859,7 +2859,9 @@ static void b43legacy_op_bss_info_changed(struct > >> >

[PATCH 2/2] PCI: iproc: add device shutdown for PCI RC

PERST# must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iProc based SoCs LCPLL clock and PERST both goes off simultaneously. This will cause certain Endpoints Intel NVMe not get detected, upon next boot sequence. This happens

[PATCH 2/2] PCI: iproc: add device shutdown for PCI RC

PERST# must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iProc based SoCs LCPLL clock and PERST both goes off simultaneously. This will cause certain Endpoints Intel NVMe not get detected, upon next boot sequence. This happens

[PATCH 1/2] PCI: iproc: Retry request when CRS returned from EP

For Configuration Requests only, following reset it is possible for a device to terminate the request but indicate that it is temporarily unable to process the Request, but will be able to process the Request in the future – in this case, the Configuration Request Retry Status 10 (CRS) Completion

[PATCH 1/2] PCI: iproc: Retry request when CRS returned from EP

For Configuration Requests only, following reset it is possible for a device to terminate the request but indicate that it is temporarily unable to process the Request, but will be able to process the Request in the future – in this case, the Configuration Request Retry Status 10 (CRS) Completion

[PATCH 0/2] PCI: iproc: SOC specific fixes.

PCI: iproc: Retry request when CRS returned from EP Above patch adds support for CRS in PCI RC driver, otherwise if not handled at lower level, the user space PMD (poll mode drivers) can timeout. PCI: iproc: add device shutdown for PCI RC This fixes the issue where certian PCI endpoints are not

[PATCH 0/2] PCI: iproc: SOC specific fixes.

PCI: iproc: Retry request when CRS returned from EP Above patch adds support for CRS in PCI RC driver, otherwise if not handled at lower level, the user space PMD (poll mode drivers) can timeout. PCI: iproc: add device shutdown for PCI RC This fixes the issue where certian PCI endpoints are not

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 05:05 +, Bart Van Assche wrote: > On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote: > > but a weeks worth of list silence for your series doesn't mean > > you're free to push un-reviewed stuff for drivers/target/ into > > linux-next. > > I think this is an

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 05:05 +, Bart Van Assche wrote: > On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote: > > but a weeks worth of list silence for your series doesn't mean > > you're free to push un-reviewed stuff for drivers/target/ into > > linux-next. > > I think this is an

Re: [PATCH] rxe: Fix a sleep-in-atomic bug in post_one_send

On Thu, Jun 01, 2017 at 09:48:34AM +0800, Jia-Ju Bai wrote: > The driver may sleep under a spin lock, and the function call path is: > post_one_send (acquire the lock by spin_lock_irqsave) > init_send_wqe > copy_from_user --> may sleep > > To fix it, the lock is released before

Re: [PATCH] rxe: Fix a sleep-in-atomic bug in post_one_send

On Thu, Jun 01, 2017 at 09:48:34AM +0800, Jia-Ju Bai wrote: > The driver may sleep under a spin lock, and the function call path is: > post_one_send (acquire the lock by spin_lock_irqsave) > init_send_wqe > copy_from_user --> may sleep > > To fix it, the lock is released before

Re: [PATCH v2 1/2] dt-bindings: timeriomem_rng: Add entropy quality property

On Mon, May 22, 2017 at 02:12:23PM -0700, Rick Altherr wrote: > Signed-off-by: Rick Altherr Both patches applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key:

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote: > but a weeks worth of list silence for your series doesn't mean > you're free to push un-reviewed stuff for drivers/target/ into > linux-next. I think this is an example of the pot calling the kettle black. Your patch "target:

Re: [PATCH v2 1/2] dt-bindings: timeriomem_rng: Add entropy quality property

On Mon, May 22, 2017 at 02:12:23PM -0700, Rick Altherr wrote: > Signed-off-by: Rick Altherr Both patches applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote: > but a weeks worth of list silence for your series doesn't mean > you're free to push un-reviewed stuff for drivers/target/ into > linux-next. I think this is an example of the pot calling the kettle black. Your patch "target:

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 04:59 +, Bart Van Assche wrote: > On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > > Hi Bart, > > > > Today's linux-next merge of the target-bva tree got a conflict in: > > > > drivers/target/target_core_transport.c > > > > between commit: > > > >

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 04:59 +, Bart Van Assche wrote: > On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > > Hi Bart, > > > > Today's linux-next merge of the target-bva tree got a conflict in: > > > > drivers/target/target_core_transport.c > > > > between commit: > > > >

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > Hi Bart, > > Today's linux-next merge of the target-bva tree got a conflict in: > > drivers/target/target_core_transport.c > > between commit: > > 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow >

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > Hi Bart, > > Today's linux-next merge of the target-bva tree got a conflict in: > > drivers/target/target_core_transport.c > > between commit: > > 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow >

[PATCH] ARM: dts: rk1108: change to "max-frequency" from "clock-freq-min-max"

"clock-freq-min-max" was deprecated. There is only using in rk1108.dtsi. Use the "max-frequency" for removiing "clock-freq-min-max" in future. Signed-off-by: Jaehoon Chung --- arch/arm/boot/dts/rk1108.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[PATCH] ARM: dts: rk1108: change to "max-frequency" from "clock-freq-min-max"

"clock-freq-min-max" was deprecated. There is only using in rk1108.dtsi. Use the "max-frequency" for removiing "clock-freq-min-max" in future. Signed-off-by: Jaehoon Chung --- arch/arm/boot/dts/rk1108.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

Michael Büsch writes: >> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c >> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c >> > @@ -2859,7 +2859,9 @@ static void b43legacy_op_bss_info_changed(struct >> > ieee80211_hw *hw, >> >b43legacy_write32(dev,

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_op_bss_info_changed

Michael Büsch writes: >> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c >> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c >> > @@ -2859,7 +2859,9 @@ static void b43legacy_op_bss_info_changed(struct >> > ieee80211_hw *hw, >> >b43legacy_write32(dev,

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > Hi Bart, > > Today's linux-next merge of the target-bva tree got a conflict in: > > drivers/target/target_core_transport.c > > between commit: > > 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow >

Re: linux-next: manual merge of the target-bva tree with the target-updates tree

On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote: > Hi Bart, > > Today's linux-next merge of the target-bva tree got a conflict in: > > drivers/target/target_core_transport.c > > between commit: > > 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow >

[PATCH] doc/ko_KR/memory-barriers: Update control-dependencies example

This commit applies upstream change, commit b26cfc48e3e0 ("doc: Update control-dependencies section of memory-barriers.txt"), to Korean translation. Signed-off-by: SeongJae Park --- Documentation/translations/ko_KR/memory-barriers.txt | 2 +- 1 file changed, 1 insertion(+),

[PATCH] doc/ko_KR/memory-barriers: Update control-dependencies example

This commit applies upstream change, commit b26cfc48e3e0 ("doc: Update control-dependencies section of memory-barriers.txt"), to Korean translation. Signed-off-by: SeongJae Park --- Documentation/translations/ko_KR/memory-barriers.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[GIT PULL] target fixes for v4.12-rc4

Hello Linus, Here are the target-pending fixes for v4.12-rc4. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master This includes: - ibmviscsis ABORT_TASK handling fixes that missed the v4.12 merge window. (Bryant Ly and Michael

[GIT PULL] target fixes for v4.12-rc4

Hello Linus, Here are the target-pending fixes for v4.12-rc4. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master This includes: - ibmviscsis ABORT_TASK handling fixes that missed the v4.12 merge window. (Bryant Ly and Michael

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_attr_interfmode_store

Jia-Ju Bai writes: >> Did you actually observe the attempt to sleep under the spin lock, >> or did you discover this using some tool? In other words, have >> either of your patches been tested? > > In fact, my reported bugs are found by a static analysis tool written > by

Re: [PATCH] b43legacy: Fix a sleep-in-atomic bug in b43legacy_attr_interfmode_store

Jia-Ju Bai writes: >> Did you actually observe the attempt to sleep under the spin lock, >> or did you discover this using some tool? In other words, have >> either of your patches been tested? > > In fact, my reported bugs are found by a static analysis tool written > by me, and they are

linux-next: manual merge of the target-bva tree with the target-updates tree

Hi Bart, Today's linux-next merge of the target-bva tree got a conflict in: drivers/target/target_core_transport.c between commit: 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow data") from the target-updates tree and commit: 2c0df665 ("target: Fix

linux-next: manual merge of the target-bva tree with the target-updates tree

Hi Bart, Today's linux-next merge of the target-bva tree got a conflict in: drivers/target/target_core_transport.c between commit: 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow data") from the target-updates tree and commit: 2c0df665 ("target: Fix

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, Jun 01, 2017 at 12:46:30PM +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > > Driver ks7010 does not currently have a maintainer. > > > > Add maintainers entry for ks7010. > > > > Signed-off-by: Tobin C. Harding > > --- > >

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, Jun 01, 2017 at 12:46:30PM +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > > Driver ks7010 does not currently have a maintainer. > > > > Add maintainers entry for ks7010. > > > > Signed-off-by: Tobin C. Harding > > --- > > MAINTAINERS | 7

Re: [RFC 1/3] staging: ks7010: move WEXT files to sub directory

On Thu, Jun 01, 2017 at 12:45:37PM +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote: > > Current driver implements the WEXT interface. WEXT is in maintenance > > mode, we need to re-write the driver using cfg80211. The current > > driver is handy as a

Re: [RFC 1/3] staging: ks7010: move WEXT files to sub directory

On Thu, Jun 01, 2017 at 12:45:37PM +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote: > > Current driver implements the WEXT interface. WEXT is in maintenance > > mode, we need to re-write the driver using cfg80211. The current > > driver is handy as a

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, 2017-06-01 at 12:46 +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > > Add maintainers entry for ks7010. [] > > diff --git a/MAINTAINERS b/MAINTAINERS [] > > @@ -7429,6 +7429,13 @@ F: Documentation/auxdisplay/ks0108 > > F:

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, 2017-06-01 at 12:46 +0900, Greg KH wrote: > On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > > Add maintainers entry for ks7010. [] > > diff --git a/MAINTAINERS b/MAINTAINERS [] > > @@ -7429,6 +7429,13 @@ F: Documentation/auxdisplay/ks0108 > > F:

[PATCH] rts5208: Fix a sleep-in-atomic bug in sd_power_off_card3v3

The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card sd_power_off_card3v3 wait_timeout schedule_timeout --> may sleep To fix it, "wait_timeout" is replaced

[PATCH] rts5208: Fix a sleep-in-atomic bug in sd_power_off_card3v3

The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card sd_power_off_card3v3 wait_timeout schedule_timeout --> may sleep To fix it, "wait_timeout" is replaced

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > Driver ks7010 does not currently have a maintainer. > > Add maintainers entry for ks7010. > > Signed-off-by: Tobin C. Harding > --- > MAINTAINERS | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git

Re: [RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote: > Driver ks7010 does not currently have a maintainer. > > Add maintainers entry for ks7010. > > Signed-off-by: Tobin C. Harding > --- > MAINTAINERS | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/MAINTAINERS

Re: [RFC 1/3] staging: ks7010: move WEXT files to sub directory

On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote: > Current driver implements the WEXT interface. WEXT is in maintenance > mode, we need to re-write the driver using cfg80211. The current > driver is handy as a reference for the new implementation, we can keep > it in tree for now.

Re: [RFC 1/3] staging: ks7010: move WEXT files to sub directory

On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote: > Current driver implements the WEXT interface. WEXT is in maintenance > mode, we need to re-write the driver using cfg80211. The current > driver is handy as a reference for the new implementation, we can keep > it in tree for now.

[PATCH] rts5208: Fix a sleep-in-atomic bug in rtsx_exclusive_enter_ss

The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card sd_cleanup_work sd_stop_seq_mode sd_switch_clock sd_ddr_tuning

[PATCH] rts5208: Fix a sleep-in-atomic bug in rtsx_exclusive_enter_ss

The driver may sleep under a spin lock, and the function call path is: rtsx_exclusive_enter_ss (acquire the lock by spin_lock) rtsx_enter_ss rtsx_power_off_card sd_cleanup_work sd_stop_seq_mode sd_switch_clock sd_ddr_tuning

Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability

Hi, On 05/31/2017 05:38 PM, Vlastimil Babka wrote: > On 05/31/2017 05:27 AM, Lu Baolu wrote: >> Hi, >> >> On 05/30/2017 09:46 PM, Vlastimil Babka wrote: >>> On 03/21/2017 09:01 AM, Lu Baolu wrote: XHCI debug capability (DbC) is an optional but standalone functionality provided by an

Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability

Hi, On 05/31/2017 05:38 PM, Vlastimil Babka wrote: > On 05/31/2017 05:27 AM, Lu Baolu wrote: >> Hi, >> >> On 05/30/2017 09:46 PM, Vlastimil Babka wrote: >>> On 03/21/2017 09:01 AM, Lu Baolu wrote: XHCI debug capability (DbC) is an optional but standalone functionality provided by an

Re: [PATCH] megaraid: Fix a sleep-in-atomic bug

On 05/31/2017 06:18 PM, Sumit Saxena wrote: -Original Message- From: Jia-Ju Bai [mailto:baijiaju1...@163.com] Sent: Wednesday, May 31, 2017 8:27 AM To: kashyap.de...@broadcom.com; sumit.sax...@broadcom.com; shivasharan.srikanteshw...@broadcom.com; j...@linux.vnet.ibm.com;

Re: [PATCH] megaraid: Fix a sleep-in-atomic bug

On 05/31/2017 06:18 PM, Sumit Saxena wrote: -Original Message- From: Jia-Ju Bai [mailto:baijiaju1...@163.com] Sent: Wednesday, May 31, 2017 8:27 AM To: kashyap.de...@broadcom.com; sumit.sax...@broadcom.com; shivasharan.srikanteshw...@broadcom.com; j...@linux.vnet.ibm.com;

Re: [v3 0/9] parallelized "struct page" zeroing

OK, so why cannot we make zero_struct_page 8x 8B stores, other arches would do memset. You said it would be slower but would that be measurable? I am sorry to be so persistent here but I would be really happier if this didn't depend on the deferred initialization. If this is absolutely a no-go

Re: [v3 0/9] parallelized "struct page" zeroing

OK, so why cannot we make zero_struct_page 8x 8B stores, other arches would do memset. You said it would be slower but would that be measurable? I am sorry to be so persistent here but I would be really happier if this didn't depend on the deferred initialization. If this is absolutely a no-go

Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability

Hi, On 05/31/2017 02:24 PM, Steven Rostedt wrote: > On Wed, 31 May 2017 11:27:19 +0800 > Lu Baolu wrote: > > + +#define XDBC_TRACE +#ifdef XDBC_TRACE +#define xdbc_trace trace_printk >>> Did you forget to remove the #define XDBC_TRACE?

Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability

Hi, On 05/31/2017 02:24 PM, Steven Rostedt wrote: > On Wed, 31 May 2017 11:27:19 +0800 > Lu Baolu wrote: > > + +#define XDBC_TRACE +#ifdef XDBC_TRACE +#define xdbc_trace trace_printk >>> Did you forget to remove the #define XDBC_TRACE? >>> >>> Enabling this driver

[RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

Driver ks7010 does not currently have a maintainer. Add maintainers entry for ks7010. Signed-off-by: Tobin C. Harding --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9e98464..75250ee 100644 --- a/MAINTAINERS +++

[RFC 3/3] MAINTAINERS: add maintainer entry for ks7010

Driver ks7010 does not currently have a maintainer. Add maintainers entry for ks7010. Signed-off-by: Tobin C. Harding --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9e98464..75250ee 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[RFC 2/3] staging: ks7010: add cfg80211 files

We are in the process of re-writing the current WEXT driver to use the cfg80211 configuration API. Currently driver root directory is empty. First step is to implement all the firmware interface in a single layer of abstraction, Firmware Interface Layer (FIL). We can add a skeleton implementation

[RFC 2/3] staging: ks7010: add cfg80211 files

We are in the process of re-writing the current WEXT driver to use the cfg80211 configuration API. Currently driver root directory is empty. First step is to implement all the firmware interface in a single layer of abstraction, Firmware Interface Layer (FIL). We can add a skeleton implementation

  1   2   3   4   5   6   7   8   9   10   >