[PATCH v5 6/8] clocksource: dmtimer: Populate the timer ops to the pdata

Add the timer ops to the platform data Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel --- Changes in v3: * Added Sebastian's Reviewed-by. Changes in v2: * No code changes in this v2 version. Only enhanced patch statistics for renames. drivers/clocksource/timer-dm.c | 25

[PATCH v5 4/8] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource

Move the dmtimer driver out of plat-omap to clocksource. So that non-omap devices also could use this. No Code changes done to the driver file only renamed to timer-dm.c. Also removed the config dependencies for OMAP_DM_TIMER. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel --- Changes

[PATCH v5 2/8] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define

Wrap the inline functions under OMAP2PLUS/OMAP1 defines. Signed-off-by: Keerthy --- arch/arm/plat-omap/include/plat/dmtimer.h | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm/plat-omap/include/plat/dmtimer.h

[PATCH v5 2/8] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define

Wrap the inline functions under OMAP2PLUS/OMAP1 defines. Signed-off-by: Keerthy --- arch/arm/plat-omap/include/plat/dmtimer.h | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm/plat-omap/include/plat/dmtimer.h b/arch/arm/plat-omap/include/plat/dmtimer.h index

[PATCH v5 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer

ATCPIT100 is often used on the Andes architecture, This timer provide 4 PIT channels. Each PIT channel is a multi-function timer, can be configured as 32,16,8 bit timers or PWM as well. For system timer it will set channel 1 32-bit timer0 as clock source and count downwards until underflow and

[PATCH v5 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer

ATCPIT100 is often used on the Andes architecture, This timer provide 4 PIT channels. Each PIT channel is a multi-function timer, can be configured as 32,16,8 bit timers or PWM as well. For system timer it will set channel 1 32-bit timer0 as clock source and count downwards until underflow and

[PATCH v5 2/3] clocksource/drivers/atcpit100: VDSO support

VDSO needs real-time cycle count to ensure the time accuracy. Unlike others, nds32 architecture does not define clock source, hence VDSO needs atcpit100 offering real-time cycle count to derive the correct time. Signed-off-by: Vincent Chen Signed-off-by: Rick Chen

[PATCH v5 2/3] clocksource/drivers/atcpit100: VDSO support

VDSO needs real-time cycle count to ensure the time accuracy. Unlike others, nds32 architecture does not define clock source, hence VDSO needs atcpit100 offering real-time cycle count to derive the correct time. Signed-off-by: Vincent Chen Signed-off-by: Rick Chen Signed-off-by: Greentime Hu

[PATCH] f2fs: fix potential hangtask in f2fs_trace_pid

As Jia-Ju Bai reported: "According to fs/f2fs/trace.c, the kernel module may sleep under a spinlock. The function call path is: f2fs_trace_pid (acquire the spinlock) f2fs_radix_tree_insert cond_resched --> may sleep I do not find a good way to fix it, so I only report. This possible bug

[PATCH] f2fs: fix potential hangtask in f2fs_trace_pid

As Jia-Ju Bai reported: "According to fs/f2fs/trace.c, the kernel module may sleep under a spinlock. The function call path is: f2fs_trace_pid (acquire the spinlock) f2fs_radix_tree_insert cond_resched --> may sleep I do not find a good way to fix it, so I only report. This possible bug

[PATCH v5 3/3] dt-bindings: timer: Add andestech atcpit100 timer binding doc

Add a document to describe Andestech atcpit100 timer and binding information. Signed-off-by: Rick Chen Signed-off-by: Greentime Hu Acked-by: Rob Herring --- .../bindings/timer/andestech,atcpit100-timer.txt | 33

[PATCH v5 0/3] Add andestech atcpit100 timer

Changelog v5: - Patch 1/3: Changes - Patch 2/3: New - Patch 3/3: Changes [Patch 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer 1 No need to split out the Makefile patch from the actual driver. Suggested by Arnd Bergmann 2 Add of_clk.name = "PCLK" to be explicit on

[PATCH v5 3/3] dt-bindings: timer: Add andestech atcpit100 timer binding doc

Add a document to describe Andestech atcpit100 timer and binding information. Signed-off-by: Rick Chen Signed-off-by: Greentime Hu Acked-by: Rob Herring --- .../bindings/timer/andestech,atcpit100-timer.txt | 33 ++ 1 file changed, 33 insertions(+) create mode 100644

[PATCH v5 0/3] Add andestech atcpit100 timer

Changelog v5: - Patch 1/3: Changes - Patch 2/3: New - Patch 3/3: Changes [Patch 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer 1 No need to split out the Makefile patch from the actual driver. Suggested by Arnd Bergmann 2 Add of_clk.name = "PCLK" to be explicit on

[PATCH] crypto: AF_ALG - limit mask and type

Hi Herbert, you see the reported problem by simply using sa.salg_mask = 0x; Note, I am not fully sure about whether CRYPTO_AF_ALG_ALLOWED_MASK and CRYPTO_AF_ALG_ALLOWED_TYPE have the correct value. But I think that all that user space should reach is potentially the ASYNC flag and the

Re: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier

Hi Laurent Pinchart, Thanks a lot for the review. On Mon, Dec 11, 2017 at 7:17 PM, Laurent Pinchart wrote: > > Hi Dhaval, > > Thank you for the patch. > > On Friday, 8 December 2017 14:35:37 EET Dhaval Shah wrote: > > SPDX-License-Identifier is used for the

[PATCH] crypto: AF_ALG - limit mask and type

Hi Herbert, you see the reported problem by simply using sa.salg_mask = 0x; Note, I am not fully sure about whether CRYPTO_AF_ALG_ALLOWED_MASK and CRYPTO_AF_ALG_ALLOWED_TYPE have the correct value. But I think that all that user space should reach is potentially the ASYNC flag and the

Re: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier

Hi Laurent Pinchart, Thanks a lot for the review. On Mon, Dec 11, 2017 at 7:17 PM, Laurent Pinchart wrote: > > Hi Dhaval, > > Thank you for the patch. > > On Friday, 8 December 2017 14:35:37 EET Dhaval Shah wrote: > > SPDX-License-Identifier is used for the Xilinx Video IP and > > related

Re: [PATCH] writeback: synchronize sync(2) against cgroup writeback membership switches

Hi Tejun, On 2017/12/12 上午3:50, Tejun Heo wrote: > sync_inodes_sb() can race against cgwb (cgroup writeback) membership > switches and fail to writeback some inodes. For example, if an inode > switches to another wb while sync_inodes_sb() is in progress, the new > wb might not be visible to

Re: [PATCH] writeback: synchronize sync(2) against cgroup writeback membership switches

Hi Tejun, On 2017/12/12 上午3:50, Tejun Heo wrote: > sync_inodes_sb() can race against cgwb (cgroup writeback) membership > switches and fail to writeback some inodes. For example, if an inode > switches to another wb while sync_inodes_sb() is in progress, the new > wb might not be visible to

[PATCH] arm64: allwinner: a64: a64-olinuxino: add usb otg

Add usb otg support for a64-olinuxino board, - USB0-ID connected with PH9 - USB0-VBUSDET connected with PH6 - USB-DRVVBUS controlled by N_VBUSEN pin from PMIC Signed-off-by: Jagan Teki --- .../boot/dts/allwinner/sun50i-a64-olinuxino.dts| 26 ++

[PATCH] arm64: allwinner: a64: a64-olinuxino: add usb otg

Add usb otg support for a64-olinuxino board, - USB0-ID connected with PH9 - USB0-VBUSDET connected with PH6 - USB-DRVVBUS controlled by N_VBUSEN pin from PMIC Signed-off-by: Jagan Teki --- .../boot/dts/allwinner/sun50i-a64-olinuxino.dts| 26 ++ 1 file changed, 26

[PATCH] KVM: X86: Fix stack-out-of-bounds read in write_mmio

From: Wanpeng Li Reported by syzkaller: BUG: KASAN: stack-out-of-bounds in write_mmio+0x11e/0x270 [kvm] Read of size 8 at addr 8803259df7f8 by task syz-executor/32298 CPU: 6 PID: 32298 Comm: syz-executor Tainted: G OE4.15.0-rc2+ #18 Hardware

[PATCH] KVM: X86: Fix stack-out-of-bounds read in write_mmio

From: Wanpeng Li Reported by syzkaller: BUG: KASAN: stack-out-of-bounds in write_mmio+0x11e/0x270 [kvm] Read of size 8 at addr 8803259df7f8 by task syz-executor/32298 CPU: 6 PID: 32298 Comm: syz-executor Tainted: G OE4.15.0-rc2+ #18 Hardware name: LENOVO

Re: [PATCH 0/8] make some functions return bool

On Mon, 11 Dec 2017, Yaowei Bai wrote: > This patchset makes some *_is_* like functions return bool because > these functions only use true or false as their return values. > > No functional changes. > I think the concern about this type of patchset in the past is that it is unnecessary churn

Re: [PATCH 0/8] make some functions return bool

On Mon, 11 Dec 2017, Yaowei Bai wrote: > This patchset makes some *_is_* like functions return bool because > these functions only use true or false as their return values. > > No functional changes. > I think the concern about this type of patchset in the past is that it is unnecessary churn

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-12 11:36 GMT+08:00 Peter Xu : > On Tue, Dec 12, 2017 at 05:51:26AM +0800, Wanpeng Li wrote: >> 2017-12-12 4:48 GMT+08:00 David Hildenbrand : >> > On 10.12.2017 22:44, Wanpeng Li wrote: >> >> From: Wanpeng Li >> >> >> >>

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-12 11:36 GMT+08:00 Peter Xu : > On Tue, Dec 12, 2017 at 05:51:26AM +0800, Wanpeng Li wrote: >> 2017-12-12 4:48 GMT+08:00 David Hildenbrand : >> > On 10.12.2017 22:44, Wanpeng Li wrote: >> >> From: Wanpeng Li >> >> >> >> [ cut here ] >> >> Bad FPU state detected at

Re: [PATCH v4] printk: Add console owner and waiter logic to load balance console writes

Hello, On (12/08/17 15:00), Petr Mladek wrote: [..] > > However, now that cross-release was introduces, lockdep can be applied > > to semaphore operations. Actually, I have a plan to do that. I think it > > would be better to make semaphore tracked with lockdep and remove all > > these manual

Re: [PATCH v4] printk: Add console owner and waiter logic to load balance console writes

Hello, On (12/08/17 15:00), Petr Mladek wrote: [..] > > However, now that cross-release was introduces, lockdep can be applied > > to semaphore operations. Actually, I have a plan to do that. I think it > > would be better to make semaphore tracked with lockdep and remove all > > these manual

[PATCH] KVM/Emulate: Mask linear address with actual address width in order to avoid conflict with UNMAPPED_GVA

Reported by syzkaller: WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.c:5631 x86_emulate_insn+0x557/0x15f0 [kvm] Modules linked in: kvm_intel kvm [last unloaded: kvm] CPU: 0 PID: 27962 Comm: syz-executor Tainted: GB W 4.15.0-rc2-next-20171208+ #32 Hardware

[PATCH] KVM/Emulate: Mask linear address with actual address width in order to avoid conflict with UNMAPPED_GVA

Reported by syzkaller: WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.c:5631 x86_emulate_insn+0x557/0x15f0 [kvm] Modules linked in: kvm_intel kvm [last unloaded: kvm] CPU: 0 PID: 27962 Comm: syz-executor Tainted: GB W 4.15.0-rc2-next-20171208+ #32 Hardware

linux-next: Tree for Dec 12

Hi all, Changes since 20171211: The clk tree still had its build failures so I used the version from next-20171208. The net-next tree gained a conflict against the net tree. The mac80211-next tree gained a build failure due to an interaction with the wireless-drivers-next tree for which I

linux-next: Tree for Dec 12

Hi all, Changes since 20171211: The clk tree still had its build failures so I used the version from next-20171208. The net-next tree gained a conflict against the net tree. The mac80211-next tree gained a build failure due to an interaction with the wireless-drivers-next tree for which I

RE: [PATCH v2 1/5] dt-bindings: rtc: add bindings for i.MX53 SRTC

>From: Fabio Estevam [mailto:feste...@gmail.com] >Sent: Dienstag, 12. Dezember 2017 00:08 >Hi Patrick, > Hi Fabio, >On Mon, Dec 11, 2017 at 5:08 AM, Patrick Brünn >wrote: > >>>rtc@... >>> >> The rtc for which this series adds support is embedded within a function >block

RE: [PATCH v2 1/5] dt-bindings: rtc: add bindings for i.MX53 SRTC

>From: Fabio Estevam [mailto:feste...@gmail.com] >Sent: Dienstag, 12. Dezember 2017 00:08 >Hi Patrick, > Hi Fabio, >On Mon, Dec 11, 2017 at 5:08 AM, Patrick Brünn >wrote: > >>>rtc@... >>> >> The rtc for which this series adds support is embedded within a function >block called >> "Secure Real

RE: [RESEND PATCH 1/2 v2] staging: fsl-mc: Allocate IRQ's before scanning DPRC objects

> -Original Message- > From: Nipun Gupta [mailto:nipun.gu...@nxp.com] > Sent: Monday, December 11, 2017 9:16 PM > To: Laurentiu Tudor ; stuyo...@gmail.com; > Bharat Bhushan ; gre...@linuxfoundation.org; > cakt...@gmail.com;

RE: [RESEND PATCH 1/2 v2] staging: fsl-mc: Allocate IRQ's before scanning DPRC objects

> -Original Message- > From: Nipun Gupta [mailto:nipun.gu...@nxp.com] > Sent: Monday, December 11, 2017 9:16 PM > To: Laurentiu Tudor ; stuyo...@gmail.com; > Bharat Bhushan ; gre...@linuxfoundation.org; > cakt...@gmail.com; bretth...@gmail.com; a...@arndb.de > Cc:

Re: [alsa-devel] [PATCH 5/8] ASoC: uniphier: add support for UniPhier AIO driver

Hello Vinod, Mark, > -Original Message- > From: Vinod Koul [mailto:vinod.k...@intel.com] > Sent: Tuesday, December 12, 2017 2:49 AM > To: Mark Brown > Cc: Suzuki, Katsuhiro/鈴木 勝博 ; > devicet...@vger.kernel.org;

Re: [alsa-devel] [PATCH 5/8] ASoC: uniphier: add support for UniPhier AIO driver

Hello Vinod, Mark, > -Original Message- > From: Vinod Koul [mailto:vinod.k...@intel.com] > Sent: Tuesday, December 12, 2017 2:49 AM > To: Mark Brown > Cc: Suzuki, Katsuhiro/鈴木 勝博 ; > devicet...@vger.kernel.org; alsa-de...@alsa-project.org; Masami Hiramatsu > ; Yamada, Masahiro/山田 真弘 > ;

Re: [RESEND PATCH V2] arm64: fault: avoid send SIGBUS two times

On 2017/12/12 11:31, Xie XiuQi wrote: >> +return 0; > It looks good to me. do_sea() has done all necessary action for SEA, so it > should always return 0, > no matter ghes_notify_sea() return true or false. yes, it is. > > Reviewed-by: Xie XiuQi Thanks XiuQi's review

Re: [RESEND PATCH V2] arm64: fault: avoid send SIGBUS two times

On 2017/12/12 11:31, Xie XiuQi wrote: >> +return 0; > It looks good to me. do_sea() has done all necessary action for SEA, so it > should always return 0, > no matter ghes_notify_sea() return true or false. yes, it is. > > Reviewed-by: Xie XiuQi Thanks XiuQi's review and comments. > >>

RE: Re: ftrace/module: Move ftrace_release_mod() to ddebug_cleanup label

Hi Steven, >> ftrace_module_init happen after dynamic_debug_setup, it is desired that >> cleanup should be called after this label however in current implementation >> it is called in free module label,ie:even though ftrace in not initialized, >> from so many fail case ftrace_release_mod() will

RE: Re: ftrace/module: Move ftrace_release_mod() to ddebug_cleanup label

Hi Steven, >> ftrace_module_init happen after dynamic_debug_setup, it is desired that >> cleanup should be called after this label however in current implementation >> it is called in free module label,ie:even though ftrace in not initialized, >> from so many fail case ftrace_release_mod() will

[PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information

The partition information was omitted during the conversion to OMAP3430 specific data. The data added by this commit is consistent with current U-Boot default definitions. Fixes: 62fe1d337461 ("ARM: dts: omap3-evm: Add OMAP3530 specific device tree processor data") Signed-off-by: Derald D. Woods

[PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information

The partition information was omitted during the conversion to OMAP3430 specific data. The data added by this commit is consistent with current U-Boot default definitions. Fixes: 62fe1d337461 ("ARM: dts: omap3-evm: Add OMAP3530 specific device tree processor data") Signed-off-by: Derald D. Woods

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Mon, 11 Dec 2017 15:54:22 +, Al Viro wrote: > Essentially, it gives helpers for work with bitfields in fixed-endian. > Suppose we have e.g. a little-endian 32bit value with fixed layout; > expressing that as a bitfield would go like > struct foo { > unsigned foo:4;

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Mon, 11 Dec 2017 15:54:22 +, Al Viro wrote: > Essentially, it gives helpers for work with bitfields in fixed-endian. > Suppose we have e.g. a little-endian 32bit value with fixed layout; > expressing that as a bitfield would go like > struct foo { > unsigned foo:4;

[BUG] drivers/gpio: some possible sleep-in-atomic bugs

According to drivers/gpio/gpio-grgpio.c, the kernel module may sleep under a spinlock. The function call paths are: grgpio_remove (acquire the spinlock) gpiochip_remove gpiochip_sysfs_unregister device_unregister --> may sleep mutex_lock --> may sleep grgpio_remove (acquire

[BUG] drivers/gpio: some possible sleep-in-atomic bugs

According to drivers/gpio/gpio-grgpio.c, the kernel module may sleep under a spinlock. The function call paths are: grgpio_remove (acquire the spinlock) gpiochip_remove gpiochip_sysfs_unregister device_unregister --> may sleep mutex_lock --> may sleep grgpio_remove (acquire

Re: [PATCH] NCR5380: Fix a possible sleep-in-atomic bug in NCR5380_poll_politely2

Thanks for your reply :) On 2017/12/12 11:38, Finn Thain wrote: On Tue, 12 Dec 2017, Jia-Ju Bai wrote: From: Jia-Ju Bai The kernel module may sleep under a spinlock. The spinlock is always taken in irq mode, and the schedule_timeout_uninterruptible() is conditional

Re: [PATCH] NCR5380: Fix a possible sleep-in-atomic bug in NCR5380_poll_politely2

Thanks for your reply :) On 2017/12/12 11:38, Finn Thain wrote: On Tue, 12 Dec 2017, Jia-Ju Bai wrote: From: Jia-Ju Bai The kernel module may sleep under a spinlock. The spinlock is always taken in irq mode, and the schedule_timeout_uninterruptible() is conditional on !irqs_disabled(). I

linux-next: build warning after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64_allmodconfig) produced this warning: drivers/misc/mic/vop/vop_vringh.c: In function 'vop_ioctl': drivers/misc/mic/vop/vop_vringh.c:1001:1: warning: label 'done' defined but not used [-Wunused-label] done: ^ Introduced

Re: [PATCH] NCR5380: Fix a possible sleep-in-atomic bug in NCR5380_poll_politely2

On Tue, 12 Dec 2017, Jia-Ju Bai wrote: > From: Jia-Ju Bai > > The kernel module may sleep under a spinlock. The spinlock is always taken in irq mode, and the schedule_timeout_uninterruptible() is conditional on !irqs_disabled(). > The function call paths are: >

linux-next: build warning after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64_allmodconfig) produced this warning: drivers/misc/mic/vop/vop_vringh.c: In function 'vop_ioctl': drivers/misc/mic/vop/vop_vringh.c:1001:1: warning: label 'done' defined but not used [-Wunused-label] done: ^ Introduced

Re: [PATCH] NCR5380: Fix a possible sleep-in-atomic bug in NCR5380_poll_politely2

On Tue, 12 Dec 2017, Jia-Ju Bai wrote: > From: Jia-Ju Bai > > The kernel module may sleep under a spinlock. The spinlock is always taken in irq mode, and the schedule_timeout_uninterruptible() is conditional on !irqs_disabled(). > The function call paths are: > NCR5380_select (acquire the

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

On Tue, Dec 12, 2017 at 05:51:26AM +0800, Wanpeng Li wrote: > 2017-12-12 4:48 GMT+08:00 David Hildenbrand : > > On 10.12.2017 22:44, Wanpeng Li wrote: > >> From: Wanpeng Li > >> > >> [ cut here ] > >> Bad FPU state detected at

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

On Tue, Dec 12, 2017 at 05:51:26AM +0800, Wanpeng Li wrote: > 2017-12-12 4:48 GMT+08:00 David Hildenbrand : > > On 10.12.2017 22:44, Wanpeng Li wrote: > >> From: Wanpeng Li > >> > >> [ cut here ] > >> Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], > >>

[BUG] 3com/3c59x: two possible sleep-in-atomic bugs

According to drivers/net/ethernet/3com/3c59x.c, the kernel module may sleep in the interrupt handler. The function call paths are: boomerang_interrupt (interrupt handler) vortex_error vortex_up pci_set_power_state --> may sleep pci_enable_device --> may sleep vortex_interrupt

[BUG] 3com/3c59x: two possible sleep-in-atomic bugs

According to drivers/net/ethernet/3com/3c59x.c, the kernel module may sleep in the interrupt handler. The function call paths are: boomerang_interrupt (interrupt handler) vortex_error vortex_up pci_set_power_state --> may sleep pci_enable_device --> may sleep vortex_interrupt

[PATCH] fix memory leak in ramoops_init

1, memory leak in ramoops_register_dummy. dummy_data = kzalloc(sizeof(*dummy_data), GFP_KERNEL); but no free when platform_device_register_data return fail 2, if kzalloc(sizeof(*dummy_data), GFP_KERNEL) return NULL, but platform_driver_register(_driver) return 0 kfree(NULL) in

[PATCH] fix memory leak in ramoops_init

1, memory leak in ramoops_register_dummy. dummy_data = kzalloc(sizeof(*dummy_data), GFP_KERNEL); but no free when platform_device_register_data return fail 2, if kzalloc(sizeof(*dummy_data), GFP_KERNEL) return NULL, but platform_driver_register(_driver) return 0 kfree(NULL) in

Re: [RESEND PATCH V2] arm64: fault: avoid send SIGBUS two times

Hi Dongjiu, On 2017/12/12 0:05, Dongjiu Geng wrote: > do_sea() calls arm64_notify_die() which will always signal > user-space. It also returns whether APEI claimed the external > abort as a RAS notification. If it returns failure do_mem_abort() > will signal user-space too. > > do_mem_abort()

Re: [RESEND PATCH V2] arm64: fault: avoid send SIGBUS two times

Hi Dongjiu, On 2017/12/12 0:05, Dongjiu Geng wrote: > do_sea() calls arm64_notify_die() which will always signal > user-space. It also returns whether APEI claimed the external > abort as a RAS notification. If it returns failure do_mem_abort() > will signal user-space too. > > do_mem_abort()

Setting large MTU size on slave interfaces may stall the whole system

(resend this email in text format) Hi, We found an issue with the bonding driver when testing Mellanox devices. The following test commands will stall the whole system sometimes, with serial console flooded with log messages from the bond_miimon_inspect() function. Setting mtu size to be

Setting large MTU size on slave interfaces may stall the whole system

(resend this email in text format) Hi, We found an issue with the bonding driver when testing Mellanox devices. The following test commands will stall the whole system sometimes, with serial console flooded with log messages from the bond_miimon_inspect() function. Setting mtu size to be

[BUG] drivers/usb/host/isp116x-hcd: a possible sleep-in-atomic bug in isp116x_start

According to drivers/usb/host/isp116x-hcd.c, the kernel module may sleep under a spinlock. The function call path is: isp116x_start (acquire the spinlock) device_init_wakeup device_wakeup_enable wakeup_source_register wakeup_source_create kmalloc(GFP_KERNEL) --> may

[BUG] drivers/usb/host/isp116x-hcd: a possible sleep-in-atomic bug in isp116x_start

According to drivers/usb/host/isp116x-hcd.c, the kernel module may sleep under a spinlock. The function call path is: isp116x_start (acquire the spinlock) device_init_wakeup device_wakeup_enable wakeup_source_register wakeup_source_create kmalloc(GFP_KERNEL) --> may

Re: a racy access flag clearing warning when calling mmap system call

> On Fri, Dec 08, 2017 at 11:19:52AM +0800, chenjiankang wrote: >> 在 2017/12/7 21:23, Will Deacon 写道: >>> diff --git a/arch/arm64/include/asm/pgtable.h >>> b/arch/arm64/include/asm/pgtable.h >>> index 149d05fb9421..8fe103b1e101 100644 >>> --- a/arch/arm64/include/asm/pgtable.h >>> +++

Re: a racy access flag clearing warning when calling mmap system call

> On Fri, Dec 08, 2017 at 11:19:52AM +0800, chenjiankang wrote: >> 在 2017/12/7 21:23, Will Deacon 写道: >>> diff --git a/arch/arm64/include/asm/pgtable.h >>> b/arch/arm64/include/asm/pgtable.h >>> index 149d05fb9421..8fe103b1e101 100644 >>> --- a/arch/arm64/include/asm/pgtable.h >>> +++

[BUG] drivers/scsi/wd719x: a possible sleep-in-atomic bug in wd719x_host_reset

According to drivers/scsi/wd719x.c, the kernel module may sleep under a spinlock. The function call path is: wd719x_host_reset (acquire the spinlock) wd719x_chip_init request_firmware --> may sleep I do not find a good way to fix it, so I only report. This possible bug is found by my

[BUG] drivers/scsi/wd719x: a possible sleep-in-atomic bug in wd719x_host_reset

According to drivers/scsi/wd719x.c, the kernel module may sleep under a spinlock. The function call path is: wd719x_host_reset (acquire the spinlock) wd719x_chip_init request_firmware --> may sleep I do not find a good way to fix it, so I only report. This possible bug is found by my

Re: [PATCH 00/13] replace print_symbol() with printk()-s

On Tue, 2017-12-12 at 11:47 +0900, Sergey Senozhatsky wrote: > On (12/11/17 08:26), Joe Perches wrote: > > On Mon, 2017-12-11 at 21:50 +0900, Sergey Senozhatsky wrote: > > > print_symbol > > Yay. > > Just about exactly 5 years earlier... > >

Re: [PATCH 00/13] replace print_symbol() with printk()-s

On Tue, 2017-12-12 at 11:47 +0900, Sergey Senozhatsky wrote: > On (12/11/17 08:26), Joe Perches wrote: > > On Mon, 2017-12-11 at 21:50 +0900, Sergey Senozhatsky wrote: > > > print_symbol > > Yay. > > Just about exactly 5 years earlier... > >

Re: [PATCH] USB: chipidea: msm: fix ulpi-node lookup

On Mon, Nov 13, 2017 at 11:12:58AM +0100, Johan Hovold wrote: > Fix child-node lookup during probe, which ended up searching the whole > device tree depth-first starting at the parent rather than just matching > on its children. > > Note that the original premature free of the parent node has

Re: [PATCH] USB: chipidea: msm: fix ulpi-node lookup

On Mon, Nov 13, 2017 at 11:12:58AM +0100, Johan Hovold wrote: > Fix child-node lookup during probe, which ended up searching the whole > device tree depth-first starting at the parent rather than just matching > on its children. > > Note that the original premature free of the parent node has

Re: [Patch v6 10/12] [media] v4l2: Add v4l2 control IDs for HEVC encoder

On Sat, 2017-12-09 at 20:48 +0200, Stanimir Varbanov wrote: > Hi Smitha, > > Thanks for the patches! > > On 12/08/2017 11:08 AM, Smitha T Murthy wrote: > > Add v4l2 controls for HEVC encoder > > > > Signed-off-by: Smitha T Murthy > > Reviewed-by: Andrzej Hajda

Re: [Patch v6 10/12] [media] v4l2: Add v4l2 control IDs for HEVC encoder

On Sat, 2017-12-09 at 20:48 +0200, Stanimir Varbanov wrote: > Hi Smitha, > > Thanks for the patches! > > On 12/08/2017 11:08 AM, Smitha T Murthy wrote: > > Add v4l2 controls for HEVC encoder > > > > Signed-off-by: Smitha T Murthy > > Reviewed-by: Andrzej Hajda > > --- > >

Re: [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace

On Mon, 11 Dec 2017, Arnaldo Carvalho de Melo wrote: > It is not working here: Hmm, I think I got it. The following construction: evts=`perf list syscalls:sys_enter_open* |& egrep 'open(at)? ' | sed -r 's/.*sys_enter_(.*) +\[.*/-e \1/'` ... expands to: "-e open -e openat" ... which is a

Re: [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace

On Mon, 11 Dec 2017, Arnaldo Carvalho de Melo wrote: > It is not working here: Hmm, I think I got it. The following construction: evts=`perf list syscalls:sys_enter_open* |& egrep 'open(at)? ' | sed -r 's/.*sys_enter_(.*) +\[.*/-e \1/'` ... expands to: "-e open -e openat" ... which is a

[BUG] drivers/scsi/ipr: two possible sleep-in-atomic bugs

According to drivers/scsi/ipr.c, the kernel module may sleep under a spinlock. The function call paths are: ipr_shutdown (acquire the spinlock) irq_poll_disable msleep --> may sleep ipr_ata_post_internal (acquire the spinlock) ipr_device_reset ipr_send_blocking_cmd

[BUG] drivers/scsi/ipr: two possible sleep-in-atomic bugs

According to drivers/scsi/ipr.c, the kernel module may sleep under a spinlock. The function call paths are: ipr_shutdown (acquire the spinlock) irq_poll_disable msleep --> may sleep ipr_ata_post_internal (acquire the spinlock) ipr_device_reset ipr_send_blocking_cmd

[PATCH 5/8] kernel/resource: iomem_is_exclusive can be boolean

This patch makes iomem_is_exclusive return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/ioport.h | 2 +- kernel/resource.c | 10 +- 2 files

[PATCH 5/8] kernel/resource: iomem_is_exclusive can be boolean

This patch makes iomem_is_exclusive return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/ioport.h | 2 +- kernel/resource.c | 10 +- 2 files changed, 6 insertions(+), 6

[PATCH 6/8] kernel/module: module_is_live can be boolean

This patch makes module_is_live return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/module.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 6/8] kernel/module: module_is_live can be boolean

This patch makes module_is_live return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/module.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/module.h

[PATCH 1/8] mm/memblock: memblock_is_map/region_memory can be boolean

This patch makes memblock_is_map/region_memory return bool due to these two functions only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/memblock.h | 4 ++-- mm/memblock.c| 6 +++---

[PATCH 1/8] mm/memblock: memblock_is_map/region_memory can be boolean

This patch makes memblock_is_map/region_memory return bool due to these two functions only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/memblock.h | 4 ++-- mm/memblock.c| 6 +++--- 2 files changed, 5

[PATCH 4/8] kernel/cpuset: current_cpuset_is_being_rebound can be boolean

This patch makes current_cpuset_is_being_rebound return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/cpuset.h | 6 +++--- kernel/cgroup/cpuset.c | 4 ++--

[PATCH 4/8] kernel/cpuset: current_cpuset_is_being_rebound can be boolean

This patch makes current_cpuset_is_being_rebound return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/cpuset.h | 6 +++--- kernel/cgroup/cpuset.c | 4 ++-- 2 files changed, 5

[PATCH 8/8] crash_dump: is_kdump_kernel can be boolean

This patch makes is_kdump_kernel return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/crash_dump.h | 10 +- 1 file changed, 5 insertions(+), 5

[PATCH 8/8] crash_dump: is_kdump_kernel can be boolean

This patch makes is_kdump_kernel return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/crash_dump.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 3/8] lib/lockref: __lockref_is_dead can be boolean

This patch makes __lockref_is_dead return bool due to this function only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/lockref.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/8] mm/mmzone: mm/lru: is_file/active_lru can be boolean

This patch makes is_file/active_lru return bool due to these two functions only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mmzone.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH 7/8] kernel/mutex: mutex_is_locked can be boolean

This patch makes mutex_is_locked return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mutex.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: [PATCH v1 2/2] usb: chipidea: tegra: Select Tegra's PHY in Kconfig

On Mon, Dec 11, 2017 at 04:09:44PM +0300, Dmitry Osipenko wrote: > On 11.12.2017 13:04, Thierry Reding wrote: > > On Mon, Dec 11, 2017 at 02:10:00AM +0300, Dmitry Osipenko wrote: > >> UDC driver won't probe without Tegra's PHY, hence select it in the > >> Kconfig. > >> > >> Signed-off-by: Dmitry

[PATCH 3/8] lib/lockref: __lockref_is_dead can be boolean

This patch makes __lockref_is_dead return bool due to this function only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/lockref.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/lockref.h

[PATCH 2/8] mm/mmzone: mm/lru: is_file/active_lru can be boolean

This patch makes is_file/active_lru return bool due to these two functions only using either true or false as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mmzone.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 7/8] kernel/mutex: mutex_is_locked can be boolean

This patch makes mutex_is_locked return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mutex.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v1 2/2] usb: chipidea: tegra: Select Tegra's PHY in Kconfig

On Mon, Dec 11, 2017 at 04:09:44PM +0300, Dmitry Osipenko wrote: > On 11.12.2017 13:04, Thierry Reding wrote: > > On Mon, Dec 11, 2017 at 02:10:00AM +0300, Dmitry Osipenko wrote: > >> UDC driver won't probe without Tegra's PHY, hence select it in the > >> Kconfig. > >> > >> Signed-off-by: Dmitry

<    1   2   3   4   5   6   7   8   9   10   >