[tip:irq/core] irqchip/qcom: Fix error handling

Commit-ID: 3900dea4cda7c28d7921370bc4d22b08463ed94c Gitweb: http://git.kernel.org/tip/3900dea4cda7c28d7921370bc4d22b08463ed94c Author: Christophe JAILLET AuthorDate: Sat, 18 Feb 2017 09:34:34 +0100 Committer: Thomas Gleixner

[tip:irq/core] irqchip/qcom: Fix error handling

Commit-ID: 3900dea4cda7c28d7921370bc4d22b08463ed94c Gitweb: http://git.kernel.org/tip/3900dea4cda7c28d7921370bc4d22b08463ed94c Author: Christophe JAILLET AuthorDate: Sat, 18 Feb 2017 09:34:34 +0100 Committer: Thomas Gleixner CommitDate: Sun, 19 Feb 2017 08:17:25 +0100 irqchip/qcom:

Re: linux-next: manual merge of the tip tree with the openrisc tree

On Fri, Feb 17, 2017 at 12:43:21PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/openrisc/include/asm/Kbuild > > between commit: > > 157e82f58007 ("openrisc: add cmpxchg and xchg implementations") > > from the openrisc

Re: linux-next: manual merge of the tip tree with the openrisc tree

On Fri, Feb 17, 2017 at 12:43:21PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/openrisc/include/asm/Kbuild > > between commit: > > 157e82f58007 ("openrisc: add cmpxchg and xchg implementations") > > from the openrisc

Re: scsi: BUG in scsi_init_io

On Tue, Jan 31, 2017 at 07:41:51AM -0800, James Bottomley wrote: > > Please-please-please, let's not use WARN for something that is not a > > kernel bug and is user-triggerable. > > It is a kernel bug and it should not be user triggerable, so it should > have a warn_on or bug_on. It means

Re: scsi: BUG in scsi_init_io

On Tue, Jan 31, 2017 at 07:41:51AM -0800, James Bottomley wrote: > > Please-please-please, let's not use WARN for something that is not a > > kernel bug and is user-triggerable. > > It is a kernel bug and it should not be user triggerable, so it should > have a warn_on or bug_on. It means

Re: [PATCH v3 4/5] vfs: Add timestamp_truncate() api

Hi Deepa, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v3 4/5] vfs: Add timestamp_truncate() api

Hi Deepa, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH repost] ptr_ring: fix race conditions when resizing

From: "Michael S. Tsirkin" Date: Sun, 19 Feb 2017 07:17:17 +0200 > Dave, could you merge this before 4.10? If not - I can try. I just sent my last pull request to Linus, please merge it to him directly. Thanks.

Re: [PATCH repost] ptr_ring: fix race conditions when resizing

From: "Michael S. Tsirkin" Date: Sun, 19 Feb 2017 07:17:17 +0200 > Dave, could you merge this before 4.10? If not - I can try. I just sent my last pull request to Linus, please merge it to him directly. Thanks.

Re: [PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Hi Byungchul, On Tue, 2017-02-14 at 16:26 +0900, Byungchul Park wrote: > Although llist provides proper APIs, they are not used. Make them used. > > Signed-off-by: Byungchul Park > --- > drivers/vhost/scsi.c | 11 +++ > 1 file changed, 3 insertions(+), 8

Re: [PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Hi Byungchul, On Tue, 2017-02-14 at 16:26 +0900, Byungchul Park wrote: > Although llist provides proper APIs, they are not used. Make them used. > > Signed-off-by: Byungchul Park > --- > drivers/vhost/scsi.c | 11 +++ > 1 file changed, 3 insertions(+), 8 deletions(-) Acked-by:

[PATCH] tools/vm: Fix possible resource leak in page_owner_sort.c

Fix possible resource leak in tools/vm/page_owner_sort.c Signed-off-by: Saurabh Badhwar --- tools/vm/page_owner_sort.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/vm/page_owner_sort.c b/tools/vm/page_owner_sort.c index

[PATCH] tools/vm: Fix possible resource leak in page_owner_sort.c

Fix possible resource leak in tools/vm/page_owner_sort.c Signed-off-by: Saurabh Badhwar --- tools/vm/page_owner_sort.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/vm/page_owner_sort.c b/tools/vm/page_owner_sort.c index f1c055f..8346261 100644 ---

Re: [PATCH] uapi: fix linux/target_core_user.h userspace compilation errors

Hi Dmitry, On Wed, 2017-02-15 at 23:04 +0300, Dmitry V. Levin wrote: > Consistently use types from linux/types.h to fix the following > linux/target_core_user.h userspace compilation errors: > > /usr/include/linux/target_core_user.h:108:4: error: unknown type name > 'uint32_t' > uint32_t

Re: [PATCH] uapi: fix linux/target_core_user.h userspace compilation errors

Hi Dmitry, On Wed, 2017-02-15 at 23:04 +0300, Dmitry V. Levin wrote: > Consistently use types from linux/types.h to fix the following > linux/target_core_user.h userspace compilation errors: > > /usr/include/linux/target_core_user.h:108:4: error: unknown type name > 'uint32_t' > uint32_t

Re: net: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected in skb_array_produce

On Sat, Feb 18, 2017 at 06:28:39PM +0100, Dmitry Vyukov wrote: > On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote: > > > > > > On 2017年02月10日 02:10, Michael S. Tsirkin wrote: > >> > >> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote: > >>> > >>> - Original

Re: net: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected in skb_array_produce

On Sat, Feb 18, 2017 at 06:28:39PM +0100, Dmitry Vyukov wrote: > On Fri, Feb 10, 2017 at 6:17 AM, Jason Wang wrote: > > > > > > On 2017年02月10日 02:10, Michael S. Tsirkin wrote: > >> > >> On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote: > >>> > >>> - Original Message - > >

[PATCH repost] ptr_ring: fix race conditions when resizing

Resizing currently drops consumer lock. This can cause entries to be reordered, which isn't good in itself. More importantly, consumer can detect a false ring empty condition and block forever. Further, nesting of consumer within producer lock is problematic for tun, since it produces entries

Re: [PATCH net-next] virito-net: set queues after reset during xdp_set

On Fri, Feb 17, 2017 at 01:10:08PM +0800, Jason Wang wrote: > > > On 2017年02月17日 12:53, John Fastabend wrote: > > On 17-02-15 01:08 AM, Jason Wang wrote: > > > We set queues before reset which will cause a crash[1]. This is > > > because is_xdp_raw_buffer_queue() depends on the old xdp queue

[PATCH repost] ptr_ring: fix race conditions when resizing

Resizing currently drops consumer lock. This can cause entries to be reordered, which isn't good in itself. More importantly, consumer can detect a false ring empty condition and block forever. Further, nesting of consumer within producer lock is problematic for tun, since it produces entries

Re: [PATCH net-next] virito-net: set queues after reset during xdp_set

On Fri, Feb 17, 2017 at 01:10:08PM +0800, Jason Wang wrote: > > > On 2017年02月17日 12:53, John Fastabend wrote: > > On 17-02-15 01:08 AM, Jason Wang wrote: > > > We set queues before reset which will cause a crash[1]. This is > > > because is_xdp_raw_buffer_queue() depends on the old xdp queue

Re: [PATCH 0/2] powerpc: kretprobe updates

On Fri, 17 Feb 2017 17:42:54 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 17, 2017 at 07:44:33PM +0900, Masami Hiramatsu escreveu: > > On Thu, 16 Feb 2017 13:47:37 +0530 > > "Naveen N. Rao" wrote: > > > > > I am posting the powerpc bits

Re: [PATCH 0/2] powerpc: kretprobe updates

On Fri, 17 Feb 2017 17:42:54 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 17, 2017 at 07:44:33PM +0900, Masami Hiramatsu escreveu: > > On Thu, 16 Feb 2017 13:47:37 +0530 > > "Naveen N. Rao" wrote: > > > > > I am posting the powerpc bits in the same thread so as to keep these > > >

Re: [PATCH][RFC v4] ACPI throttling: Disable the MSR T-state if enabled after resumed

Hi, On Sat, Feb 18, 2017 at 10:02:07AM +0100, Pavel Machek wrote: > On Fri 2017-02-17 16:27:30, Chen Yu wrote: > > Previously a bug was reported that on certain Broadwell > > platform, after resumed from S3, the CPU is running at > > an anomalously low speed, due to the BIOS has enabled the > >

Re: [PATCH][RFC v4] ACPI throttling: Disable the MSR T-state if enabled after resumed

Hi, On Sat, Feb 18, 2017 at 10:02:07AM +0100, Pavel Machek wrote: > On Fri 2017-02-17 16:27:30, Chen Yu wrote: > > Previously a bug was reported that on certain Broadwell > > platform, after resumed from S3, the CPU is running at > > an anomalously low speed, due to the BIOS has enabled the > >

[GIT] Networking

One last brown-paper-bag fix for the release. If we fail the ipv4 mapped source address check, we have to release the route. From Willem de Bruijn. Please pull, thanks a lot! The following changes since commit 2763f92f858f7c4c3198335c0542726eaed07ba3: Merge tag 'fixes-for-linus' of

[GIT] Networking

One last brown-paper-bag fix for the release. If we fail the ipv4 mapped source address check, we have to release the route. From Willem de Bruijn. Please pull, thanks a lot! The following changes since commit 2763f92f858f7c4c3198335c0542726eaed07ba3: Merge tag 'fixes-for-linus' of

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 15:35 -0500, Vivek Goyal wrote: > On Fri, Feb 17, 2017 at 09:34:07AM -0800, James Bottomley wrote: > > On Fri, 2017-02-17 at 02:55 +, Al Viro wrote: > > > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote: > > > > > > > > Hi James, > > > > > > > > > >

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Fri, 2017-02-17 at 15:35 -0500, Vivek Goyal wrote: > On Fri, Feb 17, 2017 at 09:34:07AM -0800, James Bottomley wrote: > > On Fri, 2017-02-17 at 02:55 +, Al Viro wrote: > > > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote: > > > > > > > > Hi James, > > > > > > > > > >

[PATCH 1/4] ARM64: Prepare Marvell IAP140 aka PXA1908

Suppress COMMON_CLK_PXA and MMC_PXA for now as they don't build on arm64. Also suppress the deprecated SERIAL_PXA in favor of SERIAL_8250_PXA. Signed-off-by: Andreas Färber --- arch/arm64/Kconfig.platforms | 5 + drivers/clk/Kconfig | 2 +-

[PATCH 4/4] ARM64: dts: marvell: iap140-andromeda-box-edge: Add uart0 clock

Use a fixed clock to enable ttyS0 output. Signed-off-by: Andreas Färber --- arch/arm64/boot/dts/marvell/iap140-andromeda-box-edge.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/marvell/iap140-andromeda-box-edge.dts

[PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140

Signed-off-by: Andreas Färber --- Documentation/devicetree/bindings/arm/marvell/iap140.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/marvell/iap140.txt diff --git

[PATCH 4/4] ARM64: dts: marvell: iap140-andromeda-box-edge: Add uart0 clock

Use a fixed clock to enable ttyS0 output. Signed-off-by: Andreas Färber --- arch/arm64/boot/dts/marvell/iap140-andromeda-box-edge.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/marvell/iap140-andromeda-box-edge.dts

[PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140

Signed-off-by: Andreas Färber --- Documentation/devicetree/bindings/arm/marvell/iap140.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/marvell/iap140.txt diff --git a/Documentation/devicetree/bindings/arm/marvell/iap140.txt

[PATCH 1/4] ARM64: Prepare Marvell IAP140 aka PXA1908

Suppress COMMON_CLK_PXA and MMC_PXA for now as they don't build on arm64. Also suppress the deprecated SERIAL_PXA in favor of SERIAL_8250_PXA. Signed-off-by: Andreas Färber --- arch/arm64/Kconfig.platforms | 5 + drivers/clk/Kconfig | 2 +- drivers/mmc/host/Kconfig | 2 +-

[PATCH 3/4] ARM64: dts: marvell: Add IAP140 and Andromeda Box Edge

PPI interrupts 11, 10, 9 are guesses, and so are the second two memory regions of the GIC. Signed-off-by: Andreas Färber --- arch/arm64/boot/dts/marvell/Makefile | 2 + .../boot/dts/marvell/iap140-andromeda-box-edge.dts | 70

[PATCH 0/4] ARM64: Initial Marvell IAP140 enablement

Hello, This mini-series adds initial support for the Marvell IAP140 SoC (aka PXA1908) and the Andromeda Box Edge development board. In order to enable the 8250 UART driver, it reuses ARCH_PXA; but some drivers enabled with ARCH_PXA don't build due to arm assembly or arm64's lack of mach-, so

[PATCH 3/4] ARM64: dts: marvell: Add IAP140 and Andromeda Box Edge

PPI interrupts 11, 10, 9 are guesses, and so are the second two memory regions of the GIC. Signed-off-by: Andreas Färber --- arch/arm64/boot/dts/marvell/Makefile | 2 + .../boot/dts/marvell/iap140-andromeda-box-edge.dts | 70 arch/arm64/boot/dts/marvell/iap140.dtsi

[PATCH 0/4] ARM64: Initial Marvell IAP140 enablement

Hello, This mini-series adds initial support for the Marvell IAP140 SoC (aka PXA1908) and the Andromeda Box Edge development board. In order to enable the 8250 UART driver, it reuses ARCH_PXA; but some drivers enabled with ARCH_PXA don't build due to arm assembly or arm64's lack of mach-, so

[PATCH: KS7010 Update complex macros] *Wrapping complex macros with parentheses. *Formatting changes to comply with checkpatch.

Signed-off-by: Matthew Giassa --- drivers/staging/ks7010/ks_wlan_ioctl.h | 80 +- 1 file changed, 41 insertions(+), 39 deletions(-) diff --git a/drivers/staging/ks7010/ks_wlan_ioctl.h b/drivers/staging/ks7010/ks_wlan_ioctl.h index

[PATCH: KS7010 Update complex macros] *Wrapping complex macros with parentheses. *Formatting changes to comply with checkpatch.

Signed-off-by: Matthew Giassa --- drivers/staging/ks7010/ks_wlan_ioctl.h | 80 +- 1 file changed, 41 insertions(+), 39 deletions(-) diff --git a/drivers/staging/ks7010/ks_wlan_ioctl.h b/drivers/staging/ks7010/ks_wlan_ioctl.h index 84554b6..00eec18 100644 ---

Re: [PATCH] arm64: traps: Mark __le16, __le32, __user variables properly

On Fri, Feb 17, 2017 at 08:51:12AM -0800, Stephen Boyd wrote: > Sparse complains a bit on this file about endian issues and > __user casting: > > arch/arm64/kernel/traps.c:87:37: warning: incorrect type in argument 1 > (different address spaces) > arch/arm64/kernel/traps.c:87:37:expected

Re: [PATCH] arm64: traps: Mark __le16, __le32, __user variables properly

On Fri, Feb 17, 2017 at 08:51:12AM -0800, Stephen Boyd wrote: > Sparse complains a bit on this file about endian issues and > __user casting: > > arch/arm64/kernel/traps.c:87:37: warning: incorrect type in argument 1 > (different address spaces) > arch/arm64/kernel/traps.c:87:37:expected

Re: [PATCH v3 1/5] vfs: Add file timestamp range support

On Sat, Feb 18, 2017 at 03:30:04PM -0800, Deepa Dinamani wrote: > Add fields to the superblock to track the min and max > timestamps supported by filesystems. > > Initially, when a superblock is allocated, initialize > it to the max and min values the fields can hold. > Individual filesystems

Re: [PATCH v3 1/5] vfs: Add file timestamp range support

On Sat, Feb 18, 2017 at 03:30:04PM -0800, Deepa Dinamani wrote: > Add fields to the superblock to track the min and max > timestamps supported by filesystems. > > Initially, when a superblock is allocated, initialize > it to the max and min values the fields can hold. > Individual filesystems

[GIT PULL] Thermal SoC management updates for v4.11-rc1 #1

Hello Rui, Please pull the following changes to get the Thermal SoC updates for 4.11-rc1. Here we have: - thermal support for zx2967. thanks to Baoyou Xie. - new driver support for rcar-gen3. - a couple of fixes on TI, exynos, and IMX drivers. I might also send a second pull, depending if we get

[GIT PULL] Thermal SoC management updates for v4.11-rc1 #1

Hello Rui, Please pull the following changes to get the Thermal SoC updates for 4.11-rc1. Here we have: - thermal support for zx2967. thanks to Baoyou Xie. - new driver support for rcar-gen3. - a couple of fixes on TI, exynos, and IMX drivers. I might also send a second pull, depending if we get

Re: [RESEND PATCH V5 7/8] thermal: da9062/61: Thermal junction temperature monitoring driver

Steve, On Thu, Feb 02, 2017 at 09:03:47AM +, Steve Twiss wrote: > From: Steve Twiss > > Add junction temperature monitoring supervisor device driver, compatible > with the DA9062 and DA9061 PMICs. A MODULE_DEVICE_TABLE() macro is added. > > If the PMIC's

Re: [RESEND PATCH V5 7/8] thermal: da9062/61: Thermal junction temperature monitoring driver

Steve, On Thu, Feb 02, 2017 at 09:03:47AM +, Steve Twiss wrote: > From: Steve Twiss > > Add junction temperature monitoring supervisor device driver, compatible > with the DA9062 and DA9061 PMICs. A MODULE_DEVICE_TABLE() macro is added. > > If the PMIC's internal junction temperature rises

Re: [PATCH] Thermal - Fix possible NULL derefrence.

On Tue, Feb 07, 2017 at 11:30:13AM +0800, Zhang Rui wrote: > Just one comment, > the subject should be  > [PATCH] Thermal: imx_thermal : Fix possible NULL derefrence I fixed the commit title, but I am taking this one

Re: [PATCH] Thermal - Fix possible NULL derefrence.

On Tue, Feb 07, 2017 at 11:30:13AM +0800, Zhang Rui wrote: > Just one comment, > the subject should be  > [PATCH] Thermal: imx_thermal : Fix possible NULL derefrence I fixed the commit title, but I am taking this one

Re: [PATCH] thermal: mt8173: minor mtk_thermal.c cleanups

On Mon, Feb 13, 2017 at 05:01:58PM +0800, Dawei Chien wrote: > Hi, Matthias, > > On Thu, 2017-02-09 at 22:25 +0100, Matthias Brugger wrote: > > > > On 02/08/2017 06:31 AM, Dawei Chien wrote: > > > Thermal driver should read TEMP_MSR3 if thermal bank with 4 sensors. > > > However, Currently

Re: [PATCH] thermal: mt8173: minor mtk_thermal.c cleanups

On Mon, Feb 13, 2017 at 05:01:58PM +0800, Dawei Chien wrote: > Hi, Matthias, > > On Thu, 2017-02-09 at 22:25 +0100, Matthias Brugger wrote: > > > > On 02/08/2017 06:31 AM, Dawei Chien wrote: > > > Thermal driver should read TEMP_MSR3 if thermal bank with 4 sensors. > > > However, Currently

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

On Sun, Feb 19, 2017 at 01:10:47AM +0100, Borislav Petkov wrote: Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: Good point! I noticed it too while sending out the report. It'll be showed as this in future:

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

On Sun, Feb 19, 2017 at 01:10:47AM +0100, Borislav Petkov wrote: Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: Good point! I noticed it too while sending out the report. It'll be showed as this in future:

Re: [PATCH] ARM: dts: exynos: Use thermal fuse value for thermal zone 0 on Exynos5420

On Sat, Feb 11, 2017 at 10:14:56PM +0200, Krzysztof Kozlowski wrote: > In Odroid XU3 Lite board, the temperature levels reported for thermal > zone 0 were weird. In warm room: > /sys/class/thermal/thermal_zone0/temp:32000 > /sys/class/thermal/thermal_zone1/temp:51000 >

Re: [PATCH] ARM: dts: exynos: Use thermal fuse value for thermal zone 0 on Exynos5420

On Sat, Feb 11, 2017 at 10:14:56PM +0200, Krzysztof Kozlowski wrote: > In Odroid XU3 Lite board, the temperature levels reported for thermal > zone 0 were weird. In warm room: > /sys/class/thermal/thermal_zone0/temp:32000 > /sys/class/thermal/thermal_zone1/temp:51000 >

[PATCH] arch/x86/kernel/tsc.c : set X86_FEATURE_ART for TSC on CPUs like i7-4910MQ : bug #194609

I originally reported this issue on bugzilla.kernel.org : bug # 194609 : https://bugzilla.kernel.org/show_bug.cgi?id=194609 , but it was not posted to the list . My CPU reports 'model name' as "Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz" , has 4 physical & 8 hyperthreading cores with a frequency

Re: [PATCH 3/6] perf report: Add -q/--quiet option

Hi Jiri, On Fri, Feb 17, 2017 at 12:09:35PM +0100, Jiri Olsa wrote: > On Fri, Feb 17, 2017 at 05:17:39PM +0900, Namhyung Kim wrote: > > The -q/--quiet option is to suppress any message. Sometimes users just > > want to see the numbers and it can be used for that case. > > could you put in some

[PATCH] arch/x86/kernel/tsc.c : set X86_FEATURE_ART for TSC on CPUs like i7-4910MQ : bug #194609

I originally reported this issue on bugzilla.kernel.org : bug # 194609 : https://bugzilla.kernel.org/show_bug.cgi?id=194609 , but it was not posted to the list . My CPU reports 'model name' as "Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz" , has 4 physical & 8 hyperthreading cores with a frequency

Re: [PATCH 3/6] perf report: Add -q/--quiet option

Hi Jiri, On Fri, Feb 17, 2017 at 12:09:35PM +0100, Jiri Olsa wrote: > On Fri, Feb 17, 2017 at 05:17:39PM +0900, Namhyung Kim wrote: > > The -q/--quiet option is to suppress any message. Sometimes users just > > want to see the numbers and it can be used for that case. > > could you put in some

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: > Good point! I noticed it too while sending out the report. It'll be > showed as this in future: > > > https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-Optimize-clear_page/20170210-053052 How about

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hey Fengguang, On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote: > Good point! I noticed it too while sending out the report. It'll be > showed as this in future: > > > https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-Optimize-clear_page/20170210-053052 How about

Re: [PATCH] DTS: Linksys Board: Add default trigger for sata led

Hi, Am 18.02.2017 um 15:12 schrieb Jason Cooper: > On Fri, Feb 17, 2017 at 09:42:17PM +0100, Ansuel Smith wrote: >> In others board we have the sata led set to funcion with the sata led >> trigger by default. >> This patch makes the same for these board that have sata led but disabled by >> not

Re: [PATCH] DTS: Linksys Board: Add default trigger for sata led

Hi, Am 18.02.2017 um 15:12 schrieb Jason Cooper: > On Fri, Feb 17, 2017 at 09:42:17PM +0100, Ansuel Smith wrote: >> In others board we have the sata led set to funcion with the sata led >> trigger by default. >> This patch makes the same for these board that have sata led but disabled by >> not

Re: [PATCH v2 3/3] Make vmbus register arguments read-only (fwd)

tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Eddie-Kovsky/provide-check-for-ro_after_init-memory-sections/20170218-141040 > :: branch date: 2 hours ago > :: commit date: 2 hours ago > > >> dr

Re: [PATCH v2 3/3] Make vmbus register arguments read-only (fwd)

m] > > url: > https://github.com/0day-ci/linux/commits/Eddie-Kovsky/provide-check-for-ro_after_init-memory-sections/20170218-141040 > :: branch date: 2 hours ago > :: commit date: 2 hours ago > > >> drivers/hv/vmbus_drv.c:1058:2-45: code aligned with follow

[PATCH] gcc-plugins: fix spelling mistake: "unkown" -> "unknown"

From: Colin Ian King trivial fix to spelling mistake in error message Signed-off-by: Colin Ian King --- scripts/gcc-plugins/initify_plugin.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] gcc-plugins: fix spelling mistake: "unkown" -> "unknown"

From: Colin Ian King trivial fix to spelling mistake in error message Signed-off-by: Colin Ian King --- scripts/gcc-plugins/initify_plugin.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/gcc-plugins/initify_plugin.c b/scripts/gcc-plugins/initify_plugin.c index

Re: [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote: > Hi Sebastian, > > > Am 18.02.2017 um 04:22 schrieb Sebastian Reichel : > > > > Hi, > > > > On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote: > >>> AFAIK there is no mainline board using

Re: [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, On Sat, Feb 18, 2017 at 12:33:34PM +0100, H. Nikolaus Schaller wrote: > Hi Sebastian, > > > Am 18.02.2017 um 04:22 schrieb Sebastian Reichel : > > > > Hi, > > > > On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote: > >>> AFAIK there is no mainline board using the DT except

[PATCH] fsl/fman: fix spelling mistake in variable name en_tsu_err_exeption

From: Colin Ian King trivial fix to spelling mistake, en_tsu_err_exeption should be en_tsu_err_exception Signed-off-by: Colin Ian King --- drivers/net/ethernet/freescale/fman/fman_dtsec.c | 8 1 file changed, 4 insertions(+), 4

[PATCH] fsl/fman: fix spelling mistake in variable name en_tsu_err_exeption

From: Colin Ian King trivial fix to spelling mistake, en_tsu_err_exeption should be en_tsu_err_exception Signed-off-by: Colin Ian King --- drivers/net/ethernet/freescale/fman/fman_dtsec.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

Re: [PATCH] Add pidfs filesystem

Hi Alexey, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Add pidfs filesystem

Hi Alexey, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Add pidfs filesystem

Hi Alexey, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Add pidfs filesystem

Hi Alexey, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v3 2/5] vfs: Add checks for filesystem timestamp limits

Allow read only mounts for filesystems that do not have maximum timestamps beyond the y2038 expiry timestamp. Also, allow a sysctl override to all such filesystems to be mounted with write permissions. A boot param supports initial override of these checks from the early boot without

[PATCH v3 1/5] vfs: Add file timestamp range support

Add fields to the superblock to track the min and max timestamps supported by filesystems. Initially, when a superblock is allocated, initialize it to the max and min values the fields can hold. Individual filesystems override these to match their actual limits. Pseudo filesystems are assumed to

[PATCH v3 2/5] vfs: Add checks for filesystem timestamp limits

Allow read only mounts for filesystems that do not have maximum timestamps beyond the y2038 expiry timestamp. Also, allow a sysctl override to all such filesystems to be mounted with write permissions. A boot param supports initial override of these checks from the early boot without

[PATCH v3 1/5] vfs: Add file timestamp range support

Add fields to the superblock to track the min and max timestamps supported by filesystems. Initially, when a superblock is allocated, initialize it to the max and min values the fields can hold. Individual filesystems override these to match their actual limits. Pseudo filesystems are assumed to

[PATCH v3 3/5] ext4: Initialize timestamps limits

ext4 has different overflow limits for max filesystem timestamps based on the extra bytes available. Signed-off-by: Deepa Dinamani --- fs/ext4/ext4.h | 4 fs/ext4/super.c | 7 ++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/fs/ext4/ext4.h

[PATCH v3 3/5] ext4: Initialize timestamps limits

ext4 has different overflow limits for max filesystem timestamps based on the extra bytes available. Signed-off-by: Deepa Dinamani --- fs/ext4/ext4.h | 4 fs/ext4/super.c | 7 ++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index

[PATCH v3 5/5] utimes: Clamp the timestamps before update

POSIX.1 section for futimens, utimensat and utimes says: The file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the specified time. Clamp the timestamps accordingly before assignment. Note that the clamp_t macro is used for clamping

[PATCH v3 5/5] utimes: Clamp the timestamps before update

POSIX.1 section for futimens, utimensat and utimes says: The file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the specified time. Clamp the timestamps accordingly before assignment. Note that the clamp_t macro is used for clamping

[PATCH v3 0/5] vfs: Add timestamp range check support

The series is aimed at adding timestamp checking and policy related to it to vfs. The series was developed with discussions and guidance from Arnd Bergmann. The original thread is at https://lkml.org/lkml/2016/11/2/294 Associated test: xfstests generic/402 Note that the above test will be run

[PATCH v3 0/5] vfs: Add timestamp range check support

The series is aimed at adding timestamp checking and policy related to it to vfs. The series was developed with discussions and guidance from Arnd Bergmann. The original thread is at https://lkml.org/lkml/2016/11/2/294 Associated test: xfstests generic/402 Note that the above test will be run

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sat, Feb 18, 2017 at 03:48:00PM +0100, Borislav Petkov wrote: Guys, please fix the 0day bot reporting. See below for more info. On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote: Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is

Re: [clear_page] 0ad07c8104 BUG: unable to handle kernel NULL pointer dereference at 0000000000000040

Hi Borislav, On Sat, Feb 18, 2017 at 03:48:00PM +0100, Borislav Petkov wrote: Guys, please fix the 0day bot reporting. See below for more info. On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote: Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is

[PATCH v3 4/5] vfs: Add timestamp_truncate() api

timespec_trunc() function is used to truncate a filesystem timestamp to the right granularity. But, the function does not clamp tv_sec part of the timestamps according to the filesystem timestamp limits. Also, timespec_trunc() is exclusively used for filesystem timestamps. Move the api to be part

[PATCH v3 4/5] vfs: Add timestamp_truncate() api

timespec_trunc() function is used to truncate a filesystem timestamp to the right granularity. But, the function does not clamp tv_sec part of the timestamps according to the filesystem timestamp limits. Also, timespec_trunc() is exclusively used for filesystem timestamps. Move the api to be part

Re: [PATCH] btmrvl: fix spelling mistake: "actived" -> "activated"

Hi Colin, > trivial fix to spelling mistake in error message > > Signed-off-by: Colin Ian King > --- > drivers/bluetooth/btmrvl_sdio.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel

Re: [PATCH] btmrvl: fix spelling mistake: "actived" -> "activated"

Hi Colin, > trivial fix to spelling mistake in error message > > Signed-off-by: Colin Ian King > --- > drivers/bluetooth/btmrvl_sdio.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel

Re: g_NCR5380 PDMA, was Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sat, 18 Feb 2017, Ondrej Zary wrote: > On Friday 17 February 2017 23:38:12 Finn Thain wrote: > > On Thu, 16 Feb 2017, Ondrej Zary wrote: > > > On Tuesday 31 January 2017 02:31:45 Finn Thain wrote: > > > [...] > > > > > > > Are you trying to figure out which commands are going to > > > >

Re: g_NCR5380 PDMA, was Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sat, 18 Feb 2017, Ondrej Zary wrote: > On Friday 17 February 2017 23:38:12 Finn Thain wrote: > > On Thu, 16 Feb 2017, Ondrej Zary wrote: > > > On Tuesday 31 January 2017 02:31:45 Finn Thain wrote: > > > [...] > > > > > > > Are you trying to figure out which commands are going to > > > >

Re: [PATCH] arm64: dts: hisilicon: add dts files for hi3798cv200-poplar board

Hi Jiancheng, Am 09.02.2017 um 08:07 schrieb Jiancheng Xue: > Add basic dts files for hi3798cv200-poplar board. Poplar is the > first development board compliant with the 96Boards Enterprise > Edition TV Platform specification. The board features the > Hi3798CV200 with an integrated quad-core

Re: [PATCH] arm64: dts: hisilicon: add dts files for hi3798cv200-poplar board

Hi Jiancheng, Am 09.02.2017 um 08:07 schrieb Jiancheng Xue: > Add basic dts files for hi3798cv200-poplar board. Poplar is the > first development board compliant with the 96Boards Enterprise > Edition TV Platform specification. The board features the > Hi3798CV200 with an integrated quad-core

[PATCH] net: qlogic: qla3xxx: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/qlogic/qla3xxx.c | 29

[PATCH] net: qlogic: qla3xxx: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/qlogic/qla3xxx.c | 29

  1   2   3   4   5   >