[PATCH] Documentation: Better document the hardlockup_panic sysctl

Commit ac1f591249d95372f ("kernel/watchdog.c: add sysctl knob hardlockup_panic") added the hardlockup_panic sysctl, but did not add it to Documentation/sysctl/kernel.txt. Add this, and reference it from the corresponding entry in Documentation/admin-guide/kernel-parameters.txt. Signed-off-by:

[PATCH] Documentation: Better document the hardlockup_panic sysctl

Commit ac1f591249d95372f ("kernel/watchdog.c: add sysctl knob hardlockup_panic") added the hardlockup_panic sysctl, but did not add it to Documentation/sysctl/kernel.txt. Add this, and reference it from the corresponding entry in Documentation/admin-guide/kernel-parameters.txt. Signed-off-by:

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/09/2017 09:19 AM, Pavel Machek wrote: > On Thu 2017-12-07 15:02:21, Michal Hocko wrote: >> On Thu 07-12-17 13:58:05, Cyril Hrubis wrote: >>> Hi! >> (It does seem unfortunate that the man page cannot help the programmer >> actually write correct code here. He or she is forced to read

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/09/2017 09:19 AM, Pavel Machek wrote: > On Thu 2017-12-07 15:02:21, Michal Hocko wrote: >> On Thu 07-12-17 13:58:05, Cyril Hrubis wrote: >>> Hi! >> (It does seem unfortunate that the man page cannot help the programmer >> actually write correct code here. He or she is forced to read

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Sat, 9 Dec 2017 16:21:51 +0100 Vincent Legoll wrote: > No need to get into the submenu to disable all HYPERV-related > config entries. > > This makes it easier to disable all HYPERV config options > without entering the submenu. It will also enable one > to see

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Sat, 9 Dec 2017 16:21:51 +0100 Vincent Legoll wrote: > No need to get into the submenu to disable all HYPERV-related > config entries. > > This makes it easier to disable all HYPERV config options > without entering the submenu. It will also enable one > to see that en/dis-abled state from

Re: [PATCH] kbuild: move cc-option and cc-disable-warning after incl. arch Makefile

2017-11-27 21:25 GMT+09:00 Geert Uytterhoeven : > Hi Yamada-san, > > On Mon, Nov 27, 2017 at 1:15 PM, Masahiro Yamada > wrote: >> Geert reported commit ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before >> incl. arch Makefile") broke

Re: [PATCH] kbuild: move cc-option and cc-disable-warning after incl. arch Makefile

2017-11-27 21:25 GMT+09:00 Geert Uytterhoeven : > Hi Yamada-san, > > On Mon, Nov 27, 2017 at 1:15 PM, Masahiro Yamada > wrote: >> Geert reported commit ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before >> incl. arch Makefile") broke cross-compilation using a cross-compiler >> that supports less

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, 2017-12-10 at 12:38 +0800, Xin Long wrote: > On Sun, Dec 10, 2017 at 3:36 AM, Cong Wang > wrote: > > On Fri, Dec 8, 2017 at 12:45 AM, Xin Long > > wrote: > > > This isn't a sctp problem, but mld's, seems when lo's mtu became > > > 0, > > >

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, 2017-12-10 at 12:38 +0800, Xin Long wrote: > On Sun, Dec 10, 2017 at 3:36 AM, Cong Wang > wrote: > > On Fri, Dec 8, 2017 at 12:45 AM, Xin Long > > wrote: > > > This isn't a sctp problem, but mld's, seems when lo's mtu became > > > 0, > > > it allocs a skb without enough space in

[GIT PULL] ARM: SoC fixes

Hi Linus, The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

[GIT PULL] ARM: SoC fixes

Hi Linus, The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for you to fetch changes up to

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, 2017-12-10 at 12:36 +0800, Xin Long wrote: > The new patch works to me, just two questions: > 1. should it use "idev->cnf.mtu6" here for mld ? No idea why some parts of IPv6 would use a different view of device mtu. Maybe others can comment. > > 2.  'if (int < unsigned int)' is still

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, 2017-12-10 at 12:36 +0800, Xin Long wrote: > The new patch works to me, just two questions: > 1. should it use "idev->cnf.mtu6" here for mld ? No idea why some parts of IPv6 would use a different view of device mtu. Maybe others can comment. > > 2.  'if (int < unsigned int)' is still

[PATCH v3 2/2] staging: rtl8712: Cleanup codestyle, change spaces to tabs

Cleanup below checkpatch issues: ERROR:CODE_INDENT: code indent should use tabs where possible 1409: FILE: rtl871x_security.c:1409: +from_timer(padapter, t, securitypriv.tkip_timer);$ WARNING:LEADING_SPACE: please, no spaces at the start of a line 1409: FILE:

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, Dec 10, 2017 at 3:36 AM, Cong Wang wrote: > On Fri, Dec 8, 2017 at 12:45 AM, Xin Long wrote: >> This isn't a sctp problem, but mld's, seems when lo's mtu became 0, >> it allocs a skb without enough space in add_grec(): > > Shouldn't we just

[PATCH v3 2/2] staging: rtl8712: Cleanup codestyle, change spaces to tabs

Cleanup below checkpatch issues: ERROR:CODE_INDENT: code indent should use tabs where possible 1409: FILE: rtl871x_security.c:1409: +from_timer(padapter, t, securitypriv.tkip_timer);$ WARNING:LEADING_SPACE: please, no spaces at the start of a line 1409: FILE:

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, Dec 10, 2017 at 3:36 AM, Cong Wang wrote: > On Fri, Dec 8, 2017 at 12:45 AM, Xin Long wrote: >> This isn't a sctp problem, but mld's, seems when lo's mtu became 0, >> it allocs a skb without enough space in add_grec(): > > Shouldn't we just set its min_mtu to ETH_MIN_MTU? No idea why

[PATCH v3 0/2] staging: rtl8712: Cleanup codestyle

Cleanup some codestyle issues identified by checkpatch. Changes since v2: - Modify patches so they themselves don't trigger the checkpatch issues CHECK:PARENTHESIS_ALIGNMENT and WARNING:EMAIL_SUBJECT Changes since v1: - Split single patch into multiple Neil Singh (2): staging: rtl8712:

[PATCH v3 0/2] staging: rtl8712: Cleanup codestyle

Cleanup some codestyle issues identified by checkpatch. Changes since v2: - Modify patches so they themselves don't trigger the checkpatch issues CHECK:PARENTHESIS_ALIGNMENT and WARNING:EMAIL_SUBJECT Changes since v1: - Split single patch into multiple Neil Singh (2): staging: rtl8712:

[PATCH v3 1/2] staging: rtl8712: Cleanup codestyle, break up long line

Cleanup below checkpatch issue: WARNING:LONG_LINE: line over 80 characters 1000: FILE: rtl871x_security.c:1000: +static void construct_ctr_preload(u8 *ctr_preload, sint a4_exists, sint qc_exists, Signed-off-by: Neil Singh --- drivers/staging/rtl8712/rtl871x_security.c | 5

[PATCH v3 1/2] staging: rtl8712: Cleanup codestyle, break up long line

Cleanup below checkpatch issue: WARNING:LONG_LINE: line over 80 characters 1000: FILE: rtl871x_security.c:1000: +static void construct_ctr_preload(u8 *ctr_preload, sint a4_exists, sint qc_exists, Signed-off-by: Neil Singh --- drivers/staging/rtl8712/rtl871x_security.c | 5 +++-- 1 file

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, Dec 10, 2017 at 12:59 AM, Eric Dumazet wrote: > On Sat, 2017-12-09 at 19:23 +0800, Xin Long wrote: >> On Fri, Dec 8, 2017 at 4:45 PM, Xin Long >> wrote: >> > On Fri, Dec 8, 2017 at 4:16 PM, syzbot >> >

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Sun, Dec 10, 2017 at 12:59 AM, Eric Dumazet wrote: > On Sat, 2017-12-09 at 19:23 +0800, Xin Long wrote: >> On Fri, Dec 8, 2017 at 4:45 PM, Xin Long >> wrote: >> > On Fri, Dec 8, 2017 at 4:16 PM, syzbot >> > > > .com> >> > wrote: >> > > syzkaller has found reproducer for the following crash on

Re: [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support

Hi, On Fri Aug 04, 2017 at 03:59:12PM -0400, Neil Leeder wrote: > This adds a driver for the SMMUv3 PMU into the perf framework. > It includes an IORT update to support PM Counter Groups. > In one of Cavium's upcoming SOC, SMMU PMCG implementation is such a way that platform bus id (Device ID

Re: [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support

Hi, On Fri Aug 04, 2017 at 03:59:12PM -0400, Neil Leeder wrote: > This adds a driver for the SMMUv3 PMU into the perf framework. > It includes an IORT update to support PM Counter Groups. > In one of Cavium's upcoming SOC, SMMU PMCG implementation is such a way that platform bus id (Device ID

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

Al Viro wrote: > On Sat, Dec 09, 2017 at 08:59:22PM +, Al Viro wrote: > > On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > > > On Thu 23-11-17 14:55:40, Al Viro wrote: > > > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > > > Hopefully less screwed version.

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

Al Viro wrote: > On Sat, Dec 09, 2017 at 08:59:22PM +, Al Viro wrote: > > On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > > > On Thu 23-11-17 14:55:40, Al Viro wrote: > > > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > > > Hopefully less screwed version.

Re: [PATCH v2 1/2] staging: rtl8712: Cleanup checkpatch issue WARNING:LONG_LINE

On 12/09/2017 05:11 AM, Neil Singh wrote: Cleanup below checkpatch issue: WARNING:LONG_LINE: line over 80 characters 1000: FILE: rtl871x_security.c:1000: +static void construct_ctr_preload(u8 *ctr_preload, sint a4_exists, sint qc_exists, Signed-off-by: Neil Singh ---

Re: [PATCH v2 1/2] staging: rtl8712: Cleanup checkpatch issue WARNING:LONG_LINE

On 12/09/2017 05:11 AM, Neil Singh wrote: Cleanup below checkpatch issue: WARNING:LONG_LINE: line over 80 characters 1000: FILE: rtl871x_security.c:1000: +static void construct_ctr_preload(u8 *ctr_preload, sint a4_exists, sint qc_exists, Signed-off-by: Neil Singh ---

Re: [PATCH v3 1/2] eeprom: at24: fix coding style issues

On Thu, Dec 07, 2017 at 02:39:14PM +0100, Bartosz Golaszewski wrote: > -#define AT24_DEVICE_MAGIC(_len, _flags) \ > - ((1 << AT24_SIZE_FLAGS | (_flags)) \ > +#define AT24_DEVICE_MAGIC(_len, _flags) \ > + ((1 << AT24_SIZE_FLAGS | (_flags))

Re: [PATCH v3 1/2] eeprom: at24: fix coding style issues

On Thu, Dec 07, 2017 at 02:39:14PM +0100, Bartosz Golaszewski wrote: > -#define AT24_DEVICE_MAGIC(_len, _flags) \ > - ((1 << AT24_SIZE_FLAGS | (_flags)) \ > +#define AT24_DEVICE_MAGIC(_len, _flags) \ > + ((1 << AT24_SIZE_FLAGS | (_flags))

Re: [PATCH] KVM: X86: Fix host dr6 miss restore

2017-12-08 20:39 GMT+08:00 David Hildenbrand : > On 08.12.2017 10:12, Wanpeng Li wrote: >> From: Wanpeng Li >> >> Reported by syzkaller: >> >>WARNING: CPU: 0 PID: 12927 at arch/x86/kernel/traps.c:780 >> do_debug+0x222/0x250 >>CPU: 0 PID: 12927

Re: [PATCH] KVM: X86: Fix host dr6 miss restore

2017-12-08 20:39 GMT+08:00 David Hildenbrand : > On 08.12.2017 10:12, Wanpeng Li wrote: >> From: Wanpeng Li >> >> Reported by syzkaller: >> >>WARNING: CPU: 0 PID: 12927 at arch/x86/kernel/traps.c:780 >> do_debug+0x222/0x250 >>CPU: 0 PID: 12927 Comm: syz-executor Tainted: G OE

Re: [PATCH] mtd: nand: gpio: Fix ALE gpio configuration

On Wed, Dec 6, 2017 at 6:27 PM, Christophe Leroy wrote: > Fixes a copy/paste error in commit f3d0d8d938b4d ("mtd: nand: gpio: > Convert to use GPIO descriptors") which breaks gpio-nand driver > > Fixes: f3d0d8d938b4d ("mtd: nand: gpio: Convert to use GPIO descriptors") >

Re: [PATCH] mtd: nand: gpio: Fix ALE gpio configuration

On Wed, Dec 6, 2017 at 6:27 PM, Christophe Leroy wrote: > Fixes a copy/paste error in commit f3d0d8d938b4d ("mtd: nand: gpio: > Convert to use GPIO descriptors") which breaks gpio-nand driver > > Fixes: f3d0d8d938b4d ("mtd: nand: gpio: Convert to use GPIO descriptors") > Cc: Linus Walleij >

[no subject]

Hi Lkml http://bit.ly/2y9rB7b atokawotsa

[no subject]

Hi Lkml http://bit.ly/2y9rB7b atokawotsa

[PATCH 0/4] PM / core: Direct handling of DPM_FLAG_SMART_SUSPEND and DPM_FLAG_LEAVE_SUSPENDED

Hi All, This series is a follow-up for https://marc.info/?l=linux-doc=151101644105835=2 Patches[1-3/6] from the above have been reviewed and agreed on, so they are in linux-next now and here's a next version of the rest. Patches [1-2/4] are preparatory. The first one is just really small code

[PATCH 0/4] PM / core: Direct handling of DPM_FLAG_SMART_SUSPEND and DPM_FLAG_LEAVE_SUSPENDED

Hi All, This series is a follow-up for https://marc.info/?l=linux-doc=151101644105835=2 Patches[1-3/6] from the above have been reviewed and agreed on, so they are in linux-next now and here's a next version of the rest. Patches [1-2/4] are preparatory. The first one is just really small code

[PATCH 3/4] PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization

From: Rafael J. Wysocki Make the PM core avoid invoking the "late" and "noirq" system-wide suspend (or analogous) callbacks provided by device drivers directly for devices with DPM_FLAG_SMART_SUSPEND set that are in runtime suspend during the "late" and "noirq" phases

[PATCH 3/4] PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization

From: Rafael J. Wysocki Make the PM core avoid invoking the "late" and "noirq" system-wide suspend (or analogous) callbacks provided by device drivers directly for devices with DPM_FLAG_SMART_SUSPEND set that are in runtime suspend during the "late" and "noirq" phases of system-wide suspend (or

[PATCH 1/4] PM / core: Use dev_pm_skip_next_resume_phases() internally

From: Rafael J. Wysocki Make the PM core call dev_pm_skip_next_resume_phases() to skip the "early resume" and "resume" phases of system-wide transitions to the working state for a given device instead of clearing the relevant status bits for it directly. No

[PATCH 4/4] PM / core: Direct DPM_FLAG_LEAVE_SUSPENDED handling

From: Rafael J. Wysocki Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for devices whose "noirq", "late" and "early" driver callbacks are invoked directly by it. Namely, make it skip all of the system-wide resume callbacks for such devices with

[PATCH 1/4] PM / core: Use dev_pm_skip_next_resume_phases() internally

From: Rafael J. Wysocki Make the PM core call dev_pm_skip_next_resume_phases() to skip the "early resume" and "resume" phases of system-wide transitions to the working state for a given device instead of clearing the relevant status bits for it directly. No intentional changes in functionality.

[PATCH 4/4] PM / core: Direct DPM_FLAG_LEAVE_SUSPENDED handling

From: Rafael J. Wysocki Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for devices whose "noirq", "late" and "early" driver callbacks are invoked directly by it. Namely, make it skip all of the system-wide resume callbacks for such devices with DPM_FLAG_LEAVE_SUSPENDED set if they

[PATCH 2/4] PM / core: Add helpers for subsystem callback selection

From: Rafael J. Wysocki Add helper routines to find and return a suitable subsystem callback during the "noirq" phases of system suspend/resume (or analogous) transitions as well as during the "late" phase of system suspend and the "early" phase of system resume (or

[PATCH 2/4] PM / core: Add helpers for subsystem callback selection

From: Rafael J. Wysocki Add helper routines to find and return a suitable subsystem callback during the "noirq" phases of system suspend/resume (or analogous) transitions as well as during the "late" phase of system suspend and the "early" phase of system resume (or analogous) transitions. The

Re: [PATCH net-next] libbpf: add function to setup XDP

On Sat, 9 Dec 2017 15:43:15 +0100, Eric Leblond wrote: > + for (nh = (struct nlmsghdr *)buf; NLMSG_OK(nh, len); > + nh = NLMSG_NEXT(nh, len)) { > + if (nh->nlmsg_pid != getpid()) { > + ret = -LIBBPF_ERRNO__WRNGPID; > + goto cleanup;

Re: [PATCH net-next] libbpf: add function to setup XDP

On Sat, 9 Dec 2017 15:43:15 +0100, Eric Leblond wrote: > + for (nh = (struct nlmsghdr *)buf; NLMSG_OK(nh, len); > + nh = NLMSG_NEXT(nh, len)) { > + if (nh->nlmsg_pid != getpid()) { > + ret = -LIBBPF_ERRNO__WRNGPID; > + goto cleanup;

[PATCH 0/2] iio: magnetometer: Infineon TLV493D-A1B6 support

Hello, This mini-series adds initial support for the Infineon TLV493D-A1B6 3D Magnetic Sensor found on the Infineon 3D Magnetic Sensor 2Go Kit. Tested on a Raspberry Pi 3 with a DT Overlay. https://github.com/afaerber/dt-overlays/blob/master/bcm2837-rpi-3-b%2Btlv493d-a1b6.dts Have a lot of fun!

[PATCH 0/2] iio: magnetometer: Infineon TLV493D-A1B6 support

Hello, This mini-series adds initial support for the Infineon TLV493D-A1B6 3D Magnetic Sensor found on the Infineon 3D Magnetic Sensor 2Go Kit. Tested on a Raspberry Pi 3 with a DT Overlay. https://github.com/afaerber/dt-overlays/blob/master/bcm2837-rpi-3-b%2Btlv493d-a1b6.dts Have a lot of fun!

[PATCH 1/2] dt-bindings: Add Infineon TLV493D-A1B6

The Infineon TLV493D-A1B6 is an I2C-based 3D Magnetic Sensor. Cc: Marius Tarcatu Signed-off-by: Andreas Färber --- Documentation/devicetree/bindings/trivial-devices.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/2] iio: magnetometer: Add Infineon TLV493D-A1B6

The Infineon TLV493D is a 3D magnetic sensor, A1B6 is I2C based. It is found among others on the Infineon 3D Magnetic Sensor 2Go Kit, which allows to detach the sensor as a breakout board. Cc: Marius Tarcatu Signed-off-by: Andreas Färber ---

[PATCH 1/2] dt-bindings: Add Infineon TLV493D-A1B6

The Infineon TLV493D-A1B6 is an I2C-based 3D Magnetic Sensor. Cc: Marius Tarcatu Signed-off-by: Andreas Färber --- Documentation/devicetree/bindings/trivial-devices.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/trivial-devices.txt

[PATCH 2/2] iio: magnetometer: Add Infineon TLV493D-A1B6

The Infineon TLV493D is a 3D magnetic sensor, A1B6 is I2C based. It is found among others on the Infineon 3D Magnetic Sensor 2Go Kit, which allows to detach the sensor as a breakout board. Cc: Marius Tarcatu Signed-off-by: Andreas Färber --- drivers/iio/magnetometer/Kconfig | 9 +

[PATCH] mm/slab: make calculate_alignment() function static

calculate_alignment() function is only used inside 'slab_common.c'. So make it static and let compiler do more optimizations. After this patch there's small improvements in 'text' and 'data' size. $ gcc --version gcc (GCC) 7.2.1 20171128 Before: text data bss dec hex

[PATCH] mm/slab: make calculate_alignment() function static

calculate_alignment() function is only used inside 'slab_common.c'. So make it static and let compiler do more optimizations. After this patch there's small improvements in 'text' and 'data' size. $ gcc --version gcc (GCC) 7.2.1 20171128 Before: text data bss dec hex

[alsa-devel][PATCH v3] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for the TSCS42xx audio CODEC. Add support for it. Below is the link to the v2 patch in case the threading is broken. This patch addressed each issue raised in the last review. https://patchwork.kernel.org/patch/10058117/ Signed-off-by: Steven Eckhoff

[alsa-devel][PATCH v3] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for the TSCS42xx audio CODEC. Add support for it. Below is the link to the v2 patch in case the threading is broken. This patch addressed each issue raised in the last review. https://patchwork.kernel.org/patch/10058117/ Signed-off-by: Steven Eckhoff Cc: Steven

Re: [PATCH] usb-core: Fix potential null pointer dereference in xhci-debugfs.c

Hi Mathias, thanks for the patch! The system now resumes cleanly from hibernate even with usbmuxd doing its thing. Tested-by: Alexander Kappner While testing this I hit some other issues with xhci-debugfs.c but I'll write these up in a separate bug. On 12/08/2017 09:01

Re: [PATCH] usb-core: Fix potential null pointer dereference in xhci-debugfs.c

Hi Mathias, thanks for the patch! The system now resumes cleanly from hibernate even with usbmuxd doing its thing. Tested-by: Alexander Kappner While testing this I hit some other issues with xhci-debugfs.c but I'll write these up in a separate bug. On 12/08/2017 09:01 AM, Mathias Nyman

Re: Linux 4.15-rc2: Regression in resume from ACPI S3

Hi! On Sat 2017-12-09 10:55:14, Linus Torvalds wrote: > On Dec 9, 2017 02:33, "Pavel Machek" wrote: > > > I believe I have the issue here, too (-next on thinkpad x60). Which > > patch is expected to fix it? Let me try recent -next... > > > It should be fixed in mainline. I don't

Re: Linux 4.15-rc2: Regression in resume from ACPI S3

Hi! On Sat 2017-12-09 10:55:14, Linus Torvalds wrote: > On Dec 9, 2017 02:33, "Pavel Machek" wrote: > > > I believe I have the issue here, too (-next on thinkpad x60). Which > > patch is expected to fix it? Let me try recent -next... > > > It should be fixed in mainline. I don't know if next

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Sat, Dec 09, 2017 at 08:59:22PM +, Al Viro wrote: > On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > > On Thu 23-11-17 14:55:40, Al Viro wrote: > > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > > Hopefully less screwed version. But as I've said I am

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Sat, Dec 09, 2017 at 08:59:22PM +, Al Viro wrote: > On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > > On Thu 23-11-17 14:55:40, Al Viro wrote: > > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > > Hopefully less screwed version. But as I've said I am

Re: NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps?

On Sat, 2017-12-09 at 13:03 -0800, Matt Turner wrote: > On Fri, Dec 8, 2017 at 1:16 PM, Eric Dumazet > wrote: > > On Fri, 2017-12-08 at 12:26 -0800, Matt Turner wrote: > > > > > > Thanks for the quick reply! > > > > > > I tried the patch on top of master, but

Re: NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps?

On Sat, 2017-12-09 at 13:03 -0800, Matt Turner wrote: > On Fri, Dec 8, 2017 at 1:16 PM, Eric Dumazet > wrote: > > On Fri, 2017-12-08 at 12:26 -0800, Matt Turner wrote: > > > > > > Thanks for the quick reply! > > > > > > I tried the patch on top of master, but unfortunately the > > > corruption

Re: [PATCH 1/2] platform/x86: wmi: prefix sysfs files in /sys/bus/wmi with the ACPI device

On Fri, Dec 8, 2017 at 7:41 PM, wrote: >>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello >>> wrote: >>> >>> It's possible for the same GUID to show up on as system twice. >>> This means using solely the GUID for identify the file will not

Re: [PATCH 1/2] platform/x86: wmi: prefix sysfs files in /sys/bus/wmi with the ACPI device

On Fri, Dec 8, 2017 at 7:41 PM, wrote: >>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello >>> wrote: >>> >>> It's possible for the same GUID to show up on as system twice. >>> This means using solely the GUID for identify the file will not >>> be sufficient. >> >>Isn't the file already in a

Re: [PATCH v8 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver

On 12/08/2017 12:04 AM, Dan Murphy wrote: > Rob > > > On 12/07/2017 04:49 PM, Rob Herring wrote: >> On Tue, Dec 05, 2017 at 02:46:29PM -0600, Dan Murphy wrote: >>> This adds the devicetree bindings for the LM3692x >>> I2C LED string driver. >>> >>> Acked-by: Pavel Machek >>>

Re: [PATCH v8 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver

On 12/08/2017 12:04 AM, Dan Murphy wrote: > Rob > > > On 12/07/2017 04:49 PM, Rob Herring wrote: >> On Tue, Dec 05, 2017 at 02:46:29PM -0600, Dan Murphy wrote: >>> This adds the devicetree bindings for the LM3692x >>> I2C LED string driver. >>> >>> Acked-by: Pavel Machek >>> Signed-off-by: Dan

[PATCH] serial: bfin_uart: Delete an error message for a failed memory allocation in bfin_serial_probe()

From: Markus Elfring Date: Sat, 9 Dec 2017 22:05:54 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] serial: bfin_uart: Delete an error message for a failed memory allocation in bfin_serial_probe()

From: Markus Elfring Date: Sat, 9 Dec 2017 22:05:54 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/tty/serial/bfin_uart.c | 6 ++ 1 file changed, 2

Re: NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps?

On Fri, Dec 8, 2017 at 1:16 PM, Eric Dumazet wrote: > On Fri, 2017-12-08 at 12:26 -0800, Matt Turner wrote: >> >> Thanks for the quick reply! >> >> I tried the patch on top of master, but unfortunately the corruption >> still occurs. > > You might try replacing in

Re: NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps?

On Fri, Dec 8, 2017 at 1:16 PM, Eric Dumazet wrote: > On Fri, 2017-12-08 at 12:26 -0800, Matt Turner wrote: >> >> Thanks for the quick reply! >> >> I tried the patch on top of master, but unfortunately the corruption >> still occurs. > > You might try replacing in sbdma_add_rcvbuffer() > > sb_new

Re: [PATCH 4.4 71/96] e1000e: Separate signaling for link check/link up

Hallo with this patch from here: https://marc.info/?l=linux-kernel=151272209903675=2 e1000e is great again ! :) tested 4.14.5-rc1 -- Greeting Ronald

Re: [PATCH 4.4 71/96] e1000e: Separate signaling for link check/link up

Hallo with this patch from here: https://marc.info/?l=linux-kernel=151272209903675=2 e1000e is great again ! :) tested 4.14.5-rc1 -- Greeting Ronald

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > On Thu 23-11-17 14:55:40, Al Viro wrote: > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > Hopefully less screwed version. But as I've said I am not really > > > familiar with the code and do not feel competent

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Wed, Nov 29, 2017 at 12:55:15PM +0100, Michal Hocko wrote: > On Thu 23-11-17 14:55:40, Al Viro wrote: > > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > > Hopefully less screwed version. But as I've said I am not really > > > familiar with the code and do not feel competent

Re: [PATCH 2/2] platform/x86: wmi: Allow creating WMI devices with the same GUID

On Fri, Dec 8, 2017 at 6:34 PM, Mario Limonciello wrote: > In: commit d1f9e4970742 ("ACPI: WMI: Survive BIOS with duplicate GUIDs") > parsing two of the same GUID was prevented in the WMI bus driver. > > At the time no one understood why GUID

Re: [PATCH 2/2] platform/x86: wmi: Allow creating WMI devices with the same GUID

On Fri, Dec 8, 2017 at 6:34 PM, Mario Limonciello wrote: > In: commit d1f9e4970742 ("ACPI: WMI: Survive BIOS with duplicate GUIDs") > parsing two of the same GUID was prevented in the WMI bus driver. > > At the time no one understood why GUID 05901221-D566-11D1-B2F0-00A0C9062910 > was being

[PATCH] serial: fsl_lpuart: Delete an error message for a failed memory allocation in lpuart_start_rx_dma()

From: Markus Elfring Date: Sat, 9 Dec 2017 21:34:23 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] serial: fsl_lpuart: Delete an error message for a failed memory allocation in lpuart_start_rx_dma()

From: Markus Elfring Date: Sat, 9 Dec 2017 21:34:23 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/tty/serial/fsl_lpuart.c | 4 +--- 1 file changed, 1

[PATCH v3] Staging: pi433: fix brace coding style issues in pi433_if.c

This patch fix several brace on next line, braces not necessary, space around =/<, and space before/after open/close parenthesis coding style errors find by checkpatch in pi433_if.c. Signed-off-by: Tomas Marek --- Changes in v3: - DIO0_irq_handler update reverted - will

[PATCH v3] Staging: pi433: fix brace coding style issues in pi433_if.c

This patch fix several brace on next line, braces not necessary, space around =/<, and space before/after open/close parenthesis coding style errors find by checkpatch in pi433_if.c. Signed-off-by: Tomas Marek --- Changes in v3: - DIO0_irq_handler update reverted - will be submitted in

Re: Wireless regressions in v4.15-rc1

On Sat, 2017-12-02 at 14:59 +0200, Kalle Valo wrote: > > net: netlink: Update attr validation to require exact length for some types > https://git.kernel.org/linus/28033ae4e0f5 This was reverted, more or less, to print only a warning:

Re: Wireless regressions in v4.15-rc1

On Sat, 2017-12-02 at 14:59 +0200, Kalle Valo wrote: > > net: netlink: Update attr validation to require exact length for some types > https://git.kernel.org/linus/28033ae4e0f5 This was reverted, more or less, to print only a warning:

[PATCH] i2c: update i2c-dev.h warning in documentation

`dev-interface` document gives examples for accessing i2c from userspace. There's a note warning developers about the different `i2c-dev.h` header files which were shipped with the kernel and i2c-tools separately. However, these commits in i2c-tools repository suggests that the header files are

[PATCH] i2c: update i2c-dev.h warning in documentation

`dev-interface` document gives examples for accessing i2c from userspace. There's a note warning developers about the different `i2c-dev.h` header files which were shipped with the kernel and i2c-tools separately. However, these commits in i2c-tools repository suggests that the header files are

[PATCH] i2c: update i2c-dev.h warning in documentation

`dev-interface` document gives examples for accessing i2c from userspace. There's a note warning developers about the different `i2c-dev.h` header files which were shipped with the kernel and i2c-tools separately. However, these commits in i2c-tools repository suggests that the header files are

[PATCH] i2c: update i2c-dev.h warning in documentation

`dev-interface` document gives examples for accessing i2c from userspace. There's a note warning developers about the different `i2c-dev.h` header files which were shipped with the kernel and i2c-tools separately. However, these commits in i2c-tools repository suggests that the header files are

Re: [PATCH] libsas: flush pending destruct work in sas_unregister_domain_devices()

On Thu, Dec 7, 2017 at 11:54 PM, Jason Yan wrote: > > We have sent a patchset to fix this and to enhance libsas hotplug. > Please refer to https://lkml.org/lkml/2017/9/6/142 > > And I'm going to send a new version soon. Thanks for working on it! Please make sure they will be

Re: [PATCH] libsas: flush pending destruct work in sas_unregister_domain_devices()

On Thu, Dec 7, 2017 at 11:54 PM, Jason Yan wrote: > > We have sent a patchset to fix this and to enhance libsas hotplug. > Please refer to https://lkml.org/lkml/2017/9/6/142 > > And I'm going to send a new version soon. Thanks for working on it! Please make sure they will be queued for -stable

[PATCH] dt-bindings: mailbox: ti,message-manager: Fix interrupt name error

Message Manager's mailbox interrupts are queue based and not proxy specific. The interrupt names are wrong in the binding, however correctly reflected in the example provided. Remove the relation to proxy ID in the documentation of binding. Existing device tree descriptions follow the correct

[PATCH] dt-bindings: mailbox: ti,message-manager: Fix interrupt name error

Message Manager's mailbox interrupts are queue based and not proxy specific. The interrupt names are wrong in the binding, however correctly reflected in the example provided. Remove the relation to proxy ID in the documentation of binding. Existing device tree descriptions follow the correct

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Fri, Dec 8, 2017 at 12:45 AM, Xin Long wrote: > This isn't a sctp problem, but mld's, seems when lo's mtu became 0, > it allocs a skb without enough space in add_grec(): Shouldn't we just set its min_mtu to ETH_MIN_MTU?

Re: kernel BUG at net/core/skbuff.c:LINE! (2)

On Fri, Dec 8, 2017 at 12:45 AM, Xin Long wrote: > This isn't a sctp problem, but mld's, seems when lo's mtu became 0, > it allocs a skb without enough space in add_grec(): Shouldn't we just set its min_mtu to ETH_MIN_MTU?

[PATCH 2/6] blk-mq: replace timeout synchronization with a RCU and generation based scheme

Currently, blk-mq timeout path synchronizes against the usual issue/completion path using a complex scheme involving atomic bitflags, REQ_ATOM_*, memory barriers and subtle memory coherence rules. Unfortunatley, it contains quite a few holes. There's a complex dancing around REQ_ATOM_STARTED and

[PATCH 2/6] blk-mq: replace timeout synchronization with a RCU and generation based scheme

Currently, blk-mq timeout path synchronizes against the usual issue/completion path using a complex scheme involving atomic bitflags, REQ_ATOM_*, memory barriers and subtle memory coherence rules. Unfortunatley, it contains quite a few holes. There's a complex dancing around REQ_ATOM_STARTED and

  1   2   3   4   >