[PATCH] usb: class: usblp: Fixed assignments inside if conditions

Fixed coding style issues. Signed-off-by: Alberto Ladron --- drivers/usb/class/usblp.c | 32 +--- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/drivers/usb/class/usblp.c b/drivers/usb/class/usblp.c index fb87c17..b1879ff

[PATCH] usb: class: usblp: Fixed assignments inside if conditions

Fixed coding style issues. Signed-off-by: Alberto Ladron --- drivers/usb/class/usblp.c | 32 +--- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/drivers/usb/class/usblp.c b/drivers/usb/class/usblp.c index fb87c17..b1879ff 100644 ---

[PATCH v5 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description

In commit: 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time") ... 'memmap=' was changed to adopt multiple, comma delimited values in a single entry, so update the related description. In the special case of only specifying size value without an offset, like memmap=nn[KMG],

[PATCH v5 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description

In commit: 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time") ... 'memmap=' was changed to adopt multiple, comma delimited values in a single entry, so update the related description. In the special case of only specifying size value without an offset, like memmap=nn[KMG],

[PATCH v5 2/3] KASLR: Handle memory limit specified by memmap and mem option

Option mem= will limit the max address a system can use and any memory region above the limit will be removed. Furthermore, memmap=nn[KMG] which has no offset specified has the same behaviour as mem=. KASLR needs to consider this when choosing the random position for decompressing the kernel. Do

[PATCH v5 1/3] KASLR: Parse all memmap entries in command line

In commit: f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") ... the memmap= option is parsed so that KASLR can avoid those reserved regions. It uses cmdline_find_option() to get the value if memmap= is specified, however the problem is that cmdline_find_option() can only find the

[PATCH v5 2/3] KASLR: Handle memory limit specified by memmap and mem option

Option mem= will limit the max address a system can use and any memory region above the limit will be removed. Furthermore, memmap=nn[KMG] which has no offset specified has the same behaviour as mem=. KASLR needs to consider this when choosing the random position for decompressing the kernel. Do

[PATCH v5 1/3] KASLR: Parse all memmap entries in command line

In commit: f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") ... the memmap= option is parsed so that KASLR can avoid those reserved regions. It uses cmdline_find_option() to get the value if memmap= is specified, however the problem is that cmdline_find_option() can only find the

[PATCH v5 0/3] Handle memmap and mem kernel options in boot stage kaslr

People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only

[PATCH v5 0/3] Handle memmap and mem kernel options in boot stage kaslr

People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only

Re: [PATCH v2] Add "shutdown" to "struct class".

On Fri, May 12, 2017 at 04:38:31PM -0700, Josh Zimmerman wrote: > The TPM class has some common shutdown code that must be executed for > all drivers. This adds some needed functionality for that. > > (In addition, update a comment to reflect an out-of-date path.) Change that in a different

Re: [PATCH v2] Add "shutdown" to "struct class".

On Fri, May 12, 2017 at 04:38:31PM -0700, Josh Zimmerman wrote: > The TPM class has some common shutdown code that must be executed for > all drivers. This adds some needed functionality for that. > > (In addition, update a comment to reflect an out-of-date path.) Change that in a different

Re: depmod gets stuck in symlink cycle in arch/arm/boot/dts/include

Hi, Omar! > On Fri, 12 May 2017 15:23:07 -0700, Omar Sandoval wrote: > Hi, > Linux kernel commit 4027494ae6e3 ("ARM: dts: add arm/arm64 include > symlinks") introduced a couple of symlink cycles: > $ ls -al arch/arm{,64}/boot/dts/include > arch/arm64/boot/dts/include: > total 12 >

Re: depmod gets stuck in symlink cycle in arch/arm/boot/dts/include

Hi, Omar! > On Fri, 12 May 2017 15:23:07 -0700, Omar Sandoval wrote: > Hi, > Linux kernel commit 4027494ae6e3 ("ARM: dts: add arm/arm64 include > symlinks") introduced a couple of symlink cycles: > $ ls -al arch/arm{,64}/boot/dts/include > arch/arm64/boot/dts/include: > total 12 >

[PATCH] lightnvm: pblk: fix bad free seq. on error path

Braces around the error patch for metadata pre-allocation are wrongly placed. This causes a memory leak in case of a memory allocation failure. Fix it Signed-off-by: Javier González --- drivers/lightnvm/pblk-init.c | 30 +++--- 1 file changed, 15

[PATCH] lightnvm: pblk: fix bad free seq. on error path

Braces around the error patch for metadata pre-allocation are wrongly placed. This causes a memory leak in case of a memory allocation failure. Fix it Signed-off-by: Javier González --- drivers/lightnvm/pblk-init.c | 30 +++--- 1 file changed, 15 insertions(+), 15

Re: Is there an recommended way to refer to bitkeepr commits?

Rob Landley writes: > On 05/12/2017 09:45 AM, Eric W. Biederman wrote: >> Thomas Gleixner writes: >> >>> On Fri, 12 May 2017, Michael Ellerman wrote: Fixes: BKrev: 3e8e57a1JvR25MkFRNzoz85l2Gzccg ("[PATCH] linux-2.5.66-signal-cleanup.patch")

Re: Is there an recommended way to refer to bitkeepr commits?

Rob Landley writes: > On 05/12/2017 09:45 AM, Eric W. Biederman wrote: >> Thomas Gleixner writes: >> >>> On Fri, 12 May 2017, Michael Ellerman wrote: Fixes: BKrev: 3e8e57a1JvR25MkFRNzoz85l2Gzccg ("[PATCH] linux-2.5.66-signal-cleanup.patch") In your tree that is

[PATCH v3] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

For EFI with 'efi=old_map' kernel option specified, Kernel will panic when kaslr is enabled. The back trace is: BUG: unable to handle kernel paging request at 7febd57e IP: 0x7febd57e PGD 1025a067 PUD 0 Oops: 0010 [#1] SMP [ ... ] Call Trace: ? efi_call+0x58/0x90 ? printk+0x58/0x6f

[PATCH v3] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

For EFI with 'efi=old_map' kernel option specified, Kernel will panic when kaslr is enabled. The back trace is: BUG: unable to handle kernel paging request at 7febd57e IP: 0x7febd57e PGD 1025a067 PUD 0 Oops: 0010 [#1] SMP [ ... ] Call Trace: ? efi_call+0x58/0x90 ? printk+0x58/0x6f

[PATCH] devicetree: Move include prefixes from arch to separate directory

We use a directory under arch/$ARCH/boot/dts as an include path that has links outside of the subtree to find dt-bindings from under include/dt-bindings. That's been working well, but new DT architectures haven't been adding them by default. Recently there's been a desire to share some of the DT

[PATCH] devicetree: Move include prefixes from arch to separate directory

We use a directory under arch/$ARCH/boot/dts as an include path that has links outside of the subtree to find dt-bindings from under include/dt-bindings. That's been working well, but new DT architectures haven't been adding them by default. Recently there's been a desire to share some of the DT

Re: [v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

On Sat, May 13, 2017 at 6:03 AM, kbuild test robot <l...@intel.com> wrote: > Hi Linu, > > [auto build test ERROR on arm64/for-next/core] > [also build test ERROR on v4.11 next-20170512] > [if your patch is applied to the wrong git tree, please drop us a note to > help imp

Re: [v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

On Sat, May 13, 2017 at 6:03 AM, kbuild test robot wrote: > Hi Linu, > > [auto build test ERROR on arm64/for-next/core] > [also build test ERROR on v4.11 next-20170512] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] &g

[PATCH] usb: gadget: f_fs: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/usb/gadget/function/f_fs.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/usb/gadget/function/f_fs.c

[PATCH] usb: gadget: f_fs: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/usb/gadget/function/f_fs.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c index

[PATCH] KEYS: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- security/keys/keyctl.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/security/keys/keyctl.c b/security/keys/keyctl.c index

[PATCH] USB: iowarrior: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/usb/misc/iowarrior.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c

[PATCH] KEYS: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- security/keys/keyctl.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/security/keys/keyctl.c b/security/keys/keyctl.c index dd0da25..ce1574a 100644 ---

[PATCH] USB: iowarrior: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/usb/misc/iowarrior.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c index 7756953..816afad

[PATCH] mmc: block: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/mmc/core/block.c | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c index

[PATCH] mmc: block: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/mmc/core/block.c | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c index 8273b07..47ccb2a 100644

Re: [PATCH 4.9 000/103] 4.9.28-stable review

On 05/11/2017 07:11 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.28 release. There are 103 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 000/103] 4.9.28-stable review

On 05/11/2017 07:11 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.28 release. There are 103 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

I run kernel 4.11.0-4 on a Supermicro X10SAT motherboard. HPET's enabled in BIOS, and apparently firmware table data is available. But, hpet is not an available_clocksource. Where's this need to be addressed/fixed? In my config, in kernel code, &/or in BIOS? info: @ the mobo,

HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

I run kernel 4.11.0-4 on a Supermicro X10SAT motherboard. HPET's enabled in BIOS, and apparently firmware table data is available. But, hpet is not an available_clocksource. Where's this need to be addressed/fixed? In my config, in kernel code, &/or in BIOS? info: @ the mobo,

[PATCH] ovl: Select EXPORTFS for exportfs_{en,de}code_fh

fs/overlayfs/namei.c now calls exportfs_decode_fh() and fs/overlayfs/copy_up.c calls exportfs_encode_fh() but misses an EXPORTFS select which results in the following build error: fs/built-in.o: In function `ovl_get_origin': /home/florian/dev/linux/fs/overlayfs/namei.c:141: undefined reference to

[PATCH] ovl: Select EXPORTFS for exportfs_{en,de}code_fh

fs/overlayfs/namei.c now calls exportfs_decode_fh() and fs/overlayfs/copy_up.c calls exportfs_encode_fh() but misses an EXPORTFS select which results in the following build error: fs/built-in.o: In function `ovl_get_origin': /home/florian/dev/linux/fs/overlayfs/namei.c:141: undefined reference to

Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files

On Sat, May 13, 2017 at 01:53:40AM +0300, Cyrill Gorcunov wrote: > On Sat, May 13, 2017 at 12:41:30AM +0200, Jann Horn wrote: > > [resending as plaintext] > > > > I realize that the existing kcmp code has the same issue, but: > > > > Why are you not taking a reference to filp or filp_tgt? This

Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files

On Sat, May 13, 2017 at 01:53:40AM +0300, Cyrill Gorcunov wrote: > On Sat, May 13, 2017 at 12:41:30AM +0200, Jann Horn wrote: > > [resending as plaintext] > > > > I realize that the existing kcmp code has the same issue, but: > > > > Why are you not taking a reference to filp or filp_tgt? This

[PATCH v2] staging: rtl8188eu: fix indentation error

Fixes a 'code indent should use tabs where possible' checkpatch code style error by changing whitespace into tabs. Signed-off-by: Remco Verhoef --- Changes in v2: - More expressive commit message and subject drivers/staging/rtl8188eu/hal/rtl8188e_rxdesc.c | 2 +- 1 file

[PATCH v2] staging: rtl8188eu: fix indentation error

Fixes a 'code indent should use tabs where possible' checkpatch code style error by changing whitespace into tabs. Signed-off-by: Remco Verhoef --- Changes in v2: - More expressive commit message and subject drivers/staging/rtl8188eu/hal/rtl8188e_rxdesc.c | 2 +- 1 file changed, 1

Re: [PATCH V2] SMB2: Fix share type handling

Merged into cifs-2.6.git for-next On Fri, May 12, 2017 at 10:59 AM, Christophe JAILLET wrote: > In fs/cifs/smb2pdu.h, we have: > #define SMB2_SHARE_TYPE_DISK0x01 > #define SMB2_SHARE_TYPE_PIPE0x02 > #define SMB2_SHARE_TYPE_PRINT 0x03 > > Knowing that,

Re: [PATCH V2] SMB2: Fix share type handling

Merged into cifs-2.6.git for-next On Fri, May 12, 2017 at 10:59 AM, Christophe JAILLET wrote: > In fs/cifs/smb2pdu.h, we have: > #define SMB2_SHARE_TYPE_DISK0x01 > #define SMB2_SHARE_TYPE_PIPE0x02 > #define SMB2_SHARE_TYPE_PRINT 0x03 > > Knowing that, with the current code, the

Re: [PATCH] fs: cifs: transport: Use time_after for time comparison

merged into cifs-2.6.git for-next On Thu, May 11, 2017 at 6:53 PM, Karim Eshapa wrote: > Use time_after kernel macro for time comparison > that has safety check. > > Signed-off-by: Karim Eshapa > --- > fs/cifs/transport.c | 2 +- > 1 file

Re: [PATCH] fs: cifs: transport: Use time_after for time comparison

merged into cifs-2.6.git for-next On Thu, May 11, 2017 at 6:53 PM, Karim Eshapa wrote: > Use time_after kernel macro for time comparison > that has safety check. > > Signed-off-by: Karim Eshapa > --- > fs/cifs/transport.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [v6 2/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74

Hi Linu, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.11 next-20170512] [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/Geetha-sowjanya/Cavium-ThunderX2-SMMUv3

Re: [v6 2/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74

Hi Linu, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.11 next-20170512] [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/Geetha-sowjanya/Cavium-ThunderX2-SMMUv3

[PATCH] sched: remove sched_find_first_bit()

sched_find_first_bit() is in fact the unrolled version of find_first_bit(), which is theoretically faster in some cases. But in the kernel it is called only in couple places in kernel/sched/rt.c, and both of them are not looking like hot paths that will doubtly achieve measurable benefit from

[PATCH] sched: remove sched_find_first_bit()

sched_find_first_bit() is in fact the unrolled version of find_first_bit(), which is theoretically faster in some cases. But in the kernel it is called only in couple places in kernel/sched/rt.c, and both of them are not looking like hot paths that will doubtly achieve measurable benefit from

Re: [git pull] uaccess-related bits of vfs.git

So I should have asked earlier, but I was feeling rather busy during the early merge window.. On Sun, Apr 30, 2017 at 8:45 PM, Al Viro wrote: > uaccess unification pile. It's _not_ the end of uaccess work, but > the next batch of that will go into the next

Re: [git pull] uaccess-related bits of vfs.git

So I should have asked earlier, but I was feeling rather busy during the early merge window.. On Sun, Apr 30, 2017 at 8:45 PM, Al Viro wrote: > uaccess unification pile. It's _not_ the end of uaccess work, but > the next batch of that will go into the next cycle. This one mostly takes

Re: [PATCH] cifs: cifsacl: Use a temporary ops variable to reduce code length

merged into cifs-2.6.git for-next On Tue, May 9, 2017 at 11:26 PM, Shirish Pargaonkar wrote: > Looks correct. > > Acked-by: Shirish Pargaonkar > > On Sun, May 7, 2017 at 3:31 AM, Joe Perches via samba-technical >

Re: [PATCH] cifs: cifsacl: Use a temporary ops variable to reduce code length

merged into cifs-2.6.git for-next On Tue, May 9, 2017 at 11:26 PM, Shirish Pargaonkar wrote: > Looks correct. > > Acked-by: Shirish Pargaonkar > > On Sun, May 7, 2017 at 3:31 AM, Joe Perches via samba-technical > wrote: >> Create an ops variable to store tcon->ses->server->ops and cache >>

Re: [PATCH] arm64: dts: rockchip: Drop explicit "include/" prefix from #include

On Sat, May 13, 2017 at 12:53:57AM +0100, Ian Campbell wrote: > It not necessary and counter to how all the other files are done. > > It also happens to break the build in the split device tree repo > https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ > >

Re: [PATCH] arm64: dts: rockchip: Drop explicit "include/" prefix from #include

On Sat, May 13, 2017 at 12:53:57AM +0100, Ian Campbell wrote: > It not necessary and counter to how all the other files are done. > > It also happens to break the build in the split device tree repo > https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ > >

Re: [PATCH v3 1/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

On Fri, May 12, 2017 at 05:46:06PM +0200, Matthias Brugger wrote: On 12/05/17 12:46, kbuild test robot wrote: Hi John, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.11 next-20170512] [if your patch is applied to the wrong git tree, please drop us a note to help

Re: [PATCH v3 1/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

On Fri, May 12, 2017 at 05:46:06PM +0200, Matthias Brugger wrote: On 12/05/17 12:46, kbuild test robot wrote: Hi John, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.11 next-20170512] [if your patch is applied to the wrong git tree, please drop us a note to help

Re: [PATCH] mdio: mux: fix device_node_continue.cocci warnings

On Fri, 12 May 2017, Florian Fainelli wrote: > On 05/12/2017 09:22 AM, David Miller wrote: > > From: Julia Lawall > > Date: Fri, 12 May 2017 22:54:23 +0800 (SGT) > > > >> Device node iterators put the previous value of the index variable, so an > >> explicit put causes a

Re: [PATCH] mdio: mux: fix device_node_continue.cocci warnings

On Fri, 12 May 2017, Florian Fainelli wrote: > On 05/12/2017 09:22 AM, David Miller wrote: > > From: Julia Lawall > > Date: Fri, 12 May 2017 22:54:23 +0800 (SGT) > > > >> Device node iterators put the previous value of the index variable, so an > >> explicit put causes a double put. > > ... >

Re: [v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

Hi Linu, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.11 next-20170512] [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/Geetha-sowjanya/Cavium-ThunderX2-SMMUv3

Re: [v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

Hi Linu, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.11 next-20170512] [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/Geetha-sowjanya/Cavium-ThunderX2-SMMUv3

[PATCH] arm64: dts: rockchip: Drop explicit "include/" prefix from #include

It not necessary and counter to how all the other files are done. It also happens to break the build in the split device tree repo https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ Signed-off-by: Ian Campbell Cc: Brian Norris

[PATCH] arm64: dts: rockchip: Drop explicit "include/" prefix from #include

It not necessary and counter to how all the other files are done. It also happens to break the build in the split device tree repo https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/ Signed-off-by: Ian Campbell Cc: Brian Norris Cc: Heiko Stuebner Cc: Rob

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

On 12/05/17 18:14, Tony Lindgren wrote: > * Tony Lindgren [170512 08:39]: >> * Linus Walleij [170512 02:28]: >>> On Thu, May 11, 2017 at 4:20 PM, Andre Przywara >>> wrote: Linus, can you shed some light if this array

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

On 12/05/17 18:14, Tony Lindgren wrote: > * Tony Lindgren [170512 08:39]: >> * Linus Walleij [170512 02:28]: >>> On Thu, May 11, 2017 at 4:20 PM, Andre Przywara >>> wrote: Linus, can you shed some light if this array creation serves some purpose? >>> >>> Tony [author of this function] can

Re: [RFC][PATCH 2/5] cpu-hotplug: Allow get_online_cpus() to nest

On Sat, 13 May 2017 00:15:03 +0200 (CEST) Thomas Gleixner wrote: > On Fri, 12 May 2017, Steven Rostedt wrote: > > void get_online_cpus(void) > > { > > +#ifdef CONFIG_LOCKDEP > > + if (current->goc_depth++) > > + return; > > This must be unconditional and not

Re: [RFC][PATCH 2/5] cpu-hotplug: Allow get_online_cpus() to nest

On Sat, 13 May 2017 00:15:03 +0200 (CEST) Thomas Gleixner wrote: > On Fri, 12 May 2017, Steven Rostedt wrote: > > void get_online_cpus(void) > > { > > +#ifdef CONFIG_LOCKDEP > > + if (current->goc_depth++) > > + return; > > This must be unconditional and not depend on lockdep.

Re: [PATCH 4/5] dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO

On Thu, May 11, 2017 at 03:29:24PM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki > > Thanks to work done by Broadcom explaining their USB 3.0 PHY details we > know it's attached to the MDIO bus. Use this knowledge to update the > binding: make it a subnode to the MDIO bus

Re: [PATCH 4/5] dt-bindings: phy: Modify Broadcom NS USB 3.0 PHY binding to use MDIO

On Thu, May 11, 2017 at 03:29:24PM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki > > Thanks to work done by Broadcom explaining their USB 3.0 PHY details we > know it's attached to the MDIO bus. Use this knowledge to update the > binding: make it a subnode to the MDIO bus and rework way of

Re: [PATCH v3 1/3] dt-bindings: Document STM32 I2S bindings

On Thu, May 11, 2017 at 11:45:02AM +0200, olivier moysan wrote: > Add documentation of device tree bindings for STM32 SPI/I2S. > > Signed-off-by: olivier moysan > --- > .../devicetree/bindings/sound/st,stm32-i2s.txt | 68 > ++ > 1 file changed, 68

Re: [PATCH v3 1/3] dt-bindings: Document STM32 I2S bindings

On Thu, May 11, 2017 at 11:45:02AM +0200, olivier moysan wrote: > Add documentation of device tree bindings for STM32 SPI/I2S. > > Signed-off-by: olivier moysan > --- > .../devicetree/bindings/sound/st,stm32-i2s.txt | 68 > ++ > 1 file changed, 68 insertions(+) >

[v1 1/1] usb:host:xhci support option to disable xHCI 1.0 USB2 HW LPM

XHCI specification 1.1 does not require xHCI 1.0 compliant controllers to always enable hardware USB2 LPM. However, the current xHCI driver always enable it by setting HLE=1 when seeing HLC=1. This makes certain xHCI controllers that have broken USB2 HW LPM fail to work as there is no way to

[v1 1/1] usb:host:xhci support option to disable xHCI 1.0 USB2 HW LPM

XHCI specification 1.1 does not require xHCI 1.0 compliant controllers to always enable hardware USB2 LPM. However, the current xHCI driver always enable it by setting HLE=1 when seeing HLC=1. This makes certain xHCI controllers that have broken USB2 HW LPM fail to work as there is no way to

Re: [RESEND PATCH v4 4/5] dt-bindings: usb: DT bindings documentation for Broadcom IPROC USB Device controller.

On Wed, May 10, 2017 at 06:48:08PM +0530, Raviteja Garimella wrote: > The device node is used for UDCs integrated into Broadcom's > iProc family of SoCs'. The UDC is based on Synopsys Designware > Cores AHB Subsystem USB Device Controller IP. > > Signed-off-by: Raviteja Garimella

Re: [RESEND PATCH v4 4/5] dt-bindings: usb: DT bindings documentation for Broadcom IPROC USB Device controller.

On Wed, May 10, 2017 at 06:48:08PM +0530, Raviteja Garimella wrote: > The device node is used for UDCs integrated into Broadcom's > iProc family of SoCs'. The UDC is based on Synopsys Designware > Cores AHB Subsystem USB Device Controller IP. > > Signed-off-by: Raviteja Garimella > --- >

Re: [PATCH v5 14/17] dt-bindings: slave-device: add current-speed property

On Wed, May 10, 2017 at 10:53:25AM +0200, Stefan Wahren wrote: > This adds a new DT property to define the current baud rate of the > slave device. > > Signed-off-by: Stefan Wahren > --- > Documentation/devicetree/bindings/serial/slave-device.txt | 9 + > 1 file

Re: [PATCH v5 14/17] dt-bindings: slave-device: add current-speed property

On Wed, May 10, 2017 at 10:53:25AM +0200, Stefan Wahren wrote: > This adds a new DT property to define the current baud rate of the > slave device. > > Signed-off-by: Stefan Wahren > --- > Documentation/devicetree/bindings/serial/slave-device.txt | 9 + > 1 file changed, 9 insertions(+)

Re: [PATCH v6 3/4] dt-bindings: mailbox: Introduce Qualcomm APCS global binding

On Tue, May 09, 2017 at 12:47:02PM -0700, Bjorn Andersson wrote: > Introduce a binding for the Qualcomm APCS global block, exposing a > mailbox for invoking interrupts on remote processors in the system. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v5:

Re: [PATCH v6 3/4] dt-bindings: mailbox: Introduce Qualcomm APCS global binding

On Tue, May 09, 2017 at 12:47:02PM -0700, Bjorn Andersson wrote: > Introduce a binding for the Qualcomm APCS global block, exposing a > mailbox for invoking interrupts on remote processors in the system. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v5: > - None > >

Re: [RFC/PATCH 1/2] dt-binding: mfd: Add Maxim/Dallas DS1374 MFD device binding

On Tue, May 09, 2017 at 11:20:20AM -0700, Moritz Fischer wrote: > This adds a binding for the Maxim/Dallas DS1374 MFD. > > Signed-off-by: Moritz Fischer > --- > > Hi all, > > I'm not entirely sure aobut the binding, does anyone > have a better suggestion for the

Re: [RFC/PATCH 1/2] dt-binding: mfd: Add Maxim/Dallas DS1374 MFD device binding

On Tue, May 09, 2017 at 11:20:20AM -0700, Moritz Fischer wrote: > This adds a binding for the Maxim/Dallas DS1374 MFD. > > Signed-off-by: Moritz Fischer > --- > > Hi all, > > I'm not entirely sure aobut the binding, does anyone > have a better suggestion for the remap-wdt-reset property? > >

Re: [PATCH] dt-bindings: Document optional "reserved-names" property

On Tue, May 09, 2017 at 10:18:47AM -0700, Florian Fainelli wrote: > Define an optional string property: "reserved-names" which can be used > by the client program to tag/identify reserved memory regions. > > Signed-off-by: Florian Fainelli > --- >

Re: [PATCH] dt-bindings: Document optional "reserved-names" property

On Tue, May 09, 2017 at 10:18:47AM -0700, Florian Fainelli wrote: > Define an optional string property: "reserved-names" which can be used > by the client program to tag/identify reserved memory regions. > > Signed-off-by: Florian Fainelli > --- >

Re: [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe

On Fri, May 12, 2017 at 7:34 AM, wrote: >>Yes, mostly. I've written the patch, but I was planning to target it >>at 4.12 or 4.13 but not -stable. It's mostly just a cleanup and has >>no real power saving benefit since the RSTe timeouts are so absurdly >>conservative

Re: [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe

On Fri, May 12, 2017 at 7:34 AM, wrote: >>Yes, mostly. I've written the patch, but I was planning to target it >>at 4.12 or 4.13 but not -stable. It's mostly just a cleanup and has >>no real power saving benefit since the RSTe timeouts are so absurdly >>conservative that I doubt PS4 will

[PATCH v2] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. (In addition, update a comment to reflect an out-of-date path.) Signed-off-by: Josh Zimmerman --- drivers/base/core.c| 5 +

[PATCH v2] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. (In addition, update a comment to reflect an out-of-date path.) Signed-off-by: Josh Zimmerman --- drivers/base/core.c| 5 + include/linux/device.h | 4 +++-

[PATCH] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. (In addition, update a comment to reflect an out-of-date path.) --- drivers/base/core.c| 5 + include/linux/device.h | 4 +++- 2 files changed, 8

[PATCH] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. (In addition, update a comment to reflect an out-of-date path.) --- drivers/base/core.c| 5 + include/linux/device.h | 4 +++- 2 files changed, 8

[PATCH] kmod: don't load module unless req process has CAP_SYS_MODULE

From: Mahesh Bandewar A process inside random user-ns should not load a module, which is currently possible. As demonstrated in following scenario - Create namespaces; especially a user-ns and become root inside. $ unshare -rfUp -- unshare -unm -- bash Try to load the

[PATCH] kmod: don't load module unless req process has CAP_SYS_MODULE

From: Mahesh Bandewar A process inside random user-ns should not load a module, which is currently possible. As demonstrated in following scenario - Create namespaces; especially a user-ns and become root inside. $ unshare -rfUp -- unshare -unm -- bash Try to load the bridge module. It

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, May 12, 2017 at 12:15 AM, Al Viro wrote: > Folks, seriously, have you even looked through that zoo? I have, and it's > really, really not fun. Sure, we can say "fuck 'em, no need to allow > splice() on random crap". Would be perfectly reasonable, expect that >

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, May 12, 2017 at 12:15 AM, Al Viro wrote: > Folks, seriously, have you even looked through that zoo? I have, and it's > really, really not fun. Sure, we can say "fuck 'em, no need to allow > splice() on random crap". Would be perfectly reasonable, expect that > it's not the only place

Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Mon, May 8, 2017 at 1:48 PM, Al Viro wrote: > On Mon, May 08, 2017 at 04:06:35PM +0200, Jann Horn wrote: > >> I think Kees might be talking about >> https://bugs.chromium.org/p/project-zero/issues/detail?id=822, fixed in >> commit

Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Mon, May 8, 2017 at 1:48 PM, Al Viro wrote: > On Mon, May 08, 2017 at 04:06:35PM +0200, Jann Horn wrote: > >> I think Kees might be talking about >> https://bugs.chromium.org/p/project-zero/issues/detail?id=822, fixed in >> commit e6978e4bf181fb3b5f8cb6f71b4fe30fbf1b655c. The issue was that >>

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, May 12, 2017 at 05:47:55PM -0400, Rik van Riel wrote: > > Seriously, look at these beasts.  Overwriting ->addr_limit is nowhere > > near > > the top threat.  If attacker can overwrite thread_info, you have > > lost. > > That is why THREAD_INFO_IN_TASK exists. It moves > the struct

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, May 12, 2017 at 05:47:55PM -0400, Rik van Riel wrote: > > Seriously, look at these beasts.  Overwriting ->addr_limit is nowhere > > near > > the top threat.  If attacker can overwrite thread_info, you have > > lost. > > That is why THREAD_INFO_IN_TASK exists. It moves > the struct

Re: [PATCH v3 1/2] selinux: add brief info to policydb

On Fri, May 12, 2017 at 3:22 PM, Paul Moore wrote: > > On Thu, May 11, 2017 at 4:45 PM, Casey Schaufler > wrote: > > On 5/11/2017 1:22 PM, Stephen Smalley wrote: > >> On Thu, 2017-05-11 at 08:56 -0700, Casey Schaufler wrote: > >>> On 5/11/2017 5:59

Re: [PATCH v3 1/2] selinux: add brief info to policydb

On Fri, May 12, 2017 at 3:22 PM, Paul Moore wrote: > > On Thu, May 11, 2017 at 4:45 PM, Casey Schaufler > wrote: > > On 5/11/2017 1:22 PM, Stephen Smalley wrote: > >> On Thu, 2017-05-11 at 08:56 -0700, Casey Schaufler wrote: > >>> On 5/11/2017 5:59 AM, Sebastien Buisson wrote: > Add

  1   2   3   4   5   6   7   8   9   10   >