Re: INFO: rcu detected stall in shrink_dentry_list

On Sat, Apr 14, 2018 at 11:43 AM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 16e205cf42da1f497b10a4a24f563e6c0d574eec (Fri Apr 13 03:56:10 2018 +) > Merge tag 'drm-fixes-for-v4.17-rc1' of >

Re: INFO: rcu detected stall in shrink_dentry_list

On Sat, Apr 14, 2018 at 11:43 AM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 16e205cf42da1f497b10a4a24f563e6c0d574eec (Fri Apr 13 03:56:10 2018 +) > Merge tag 'drm-fixes-for-v4.17-rc1' of > git://people.freedesktop.org/~airlied/linux > syzbot dashboard

INFO: rcu detected stall in shrink_dentry_list

Hello, syzbot hit the following crash on upstream commit 16e205cf42da1f497b10a4a24f563e6c0d574eec (Fri Apr 13 03:56:10 2018 +) Merge tag 'drm-fixes-for-v4.17-rc1' of git://people.freedesktop.org/~airlied/linux syzbot dashboard link:

INFO: rcu detected stall in shrink_dentry_list

Hello, syzbot hit the following crash on upstream commit 16e205cf42da1f497b10a4a24f563e6c0d574eec (Fri Apr 13 03:56:10 2018 +) Merge tag 'drm-fixes-for-v4.17-rc1' of git://people.freedesktop.org/~airlied/linux syzbot dashboard link:

kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared

Hi, Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN undeclared. Searching string related to KMOD_DECOMP_LEN in linux-4.9.94 and linux-4.15.17 sources as below: sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.15.17 ./linux-4.15.17/tools/perf/tests/code-reading.c: char

kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared

Hi, Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN undeclared. Searching string related to KMOD_DECOMP_LEN in linux-4.9.94 and linux-4.15.17 sources as below: sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.15.17 ./linux-4.15.17/tools/perf/tests/code-reading.c: char

[PATCH v3] net: davicom: dm9000: Avoid spinlock recursion during dm9000_timeout routine

On the DM9000B, dm9000_phy_write() is called after the main spinlock is held, during the dm9000_timeout() routine. Spinlock recursion occurs because the main spinlock is requested again in dm9000_phy_write(). So spinlock should be avoided in phy operation during the dm9000_timeout() routine. ---

[PATCH v3] net: davicom: dm9000: Avoid spinlock recursion during dm9000_timeout routine

On the DM9000B, dm9000_phy_write() is called after the main spinlock is held, during the dm9000_timeout() routine. Spinlock recursion occurs because the main spinlock is requested again in dm9000_phy_write(). So spinlock should be avoided in phy operation during the dm9000_timeout() routine. ---

Re: [PATCH v1 1/1] usb: core: Add quirk for HP v222w 16GB Mini

Hello! On 4/13/2018 8:40 PM, sathyanarayanan.kuppusw...@linux.intel.com wrote: From: Kamil Lulko Add DELAY_INIT quirk to fix the following problem with HP v222w 16GB Mini: usb 1-3: unable to read config index 0 descriptor/start: -110 usb 1-3: can't read

Re: [PATCH v1 1/1] usb: core: Add quirk for HP v222w 16GB Mini

Hello! On 4/13/2018 8:40 PM, sathyanarayanan.kuppusw...@linux.intel.com wrote: From: Kamil Lulko Add DELAY_INIT quirk to fix the following problem with HP v222w 16GB Mini: usb 1-3: unable to read config index 0 descriptor/start: -110 usb 1-3: can't read configurations, error -110 usb 1-3:

Re: [PATCH] fs/dcache.c: re-add cond_resched() in shrink_dcache_parent()

On Sat, Apr 14, 2018 at 10:00:29AM +0300, Nikolay Borisov wrote: > > > On 14.04.2018 00:14, Andrew Morton wrote: > > On Fri, 13 Apr 2018 13:28:23 -0700 Khazhismel Kumykov > > wrote: > > > >> shrink_dcache_parent may spin waiting for a parallel shrink_dentry_list. > >> In

Re: [PATCH] fs/dcache.c: re-add cond_resched() in shrink_dcache_parent()

On Sat, Apr 14, 2018 at 10:00:29AM +0300, Nikolay Borisov wrote: > > > On 14.04.2018 00:14, Andrew Morton wrote: > > On Fri, 13 Apr 2018 13:28:23 -0700 Khazhismel Kumykov > > wrote: > > > >> shrink_dcache_parent may spin waiting for a parallel shrink_dentry_list. > >> In this case we may have

Re: [PATCH] fs: avoid fdput() after failed fdget() in vfs_dedupe_file_range()

On Sat, Apr 14, 2018 at 01:16:58AM -0500, Zev Weiss wrote: > It's a fairly inconsequential bug, since fdput() won't actually try to > fput() the file due to fd.flags (and thus FDPUT_FPUT) being zero in > the failure case, but most other vfs code takes steps to avoid this. Applied.

Re: [PATCH] fs: avoid fdput() after failed fdget() in vfs_dedupe_file_range()

On Sat, Apr 14, 2018 at 01:16:58AM -0500, Zev Weiss wrote: > It's a fairly inconsequential bug, since fdput() won't actually try to > fput() the file due to fd.flags (and thus FDPUT_FPUT) being zero in > the failure case, but most other vfs code takes steps to avoid this. Applied.

Re: INFO: rcu detected stall in do_raw_spin_unlock

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in do_raw_spin_unlock

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in _raw_spin_unlock

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in shrink_dcache_parent

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in vfs_rmdir

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in shrink_dcache_parent

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in vfs_rmdir

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: INFO: rcu detected stall in _raw_spin_unlock

Infinite loop inside shrink_dcache_parent() due to lack of cond_resched(). I can reproduce this issue by running the reproducer on one CPU (using "taskset -c 0"). Reverting commit 32785c0539b7e96f ("fs/dcache.c: add cond_resched() in shrink_dentry_list()") solves this issue. #syz dup: INFO: rcu

Re: [PATCH] fs/dcache.c: re-add cond_resched() in shrink_dcache_parent()

On 14.04.2018 00:14, Andrew Morton wrote: > On Fri, 13 Apr 2018 13:28:23 -0700 Khazhismel Kumykov > wrote: > >> shrink_dcache_parent may spin waiting for a parallel shrink_dentry_list. >> In this case we may have 0 dentries to dispose, so we will never >> schedule out while

Re: [PATCH] fs/dcache.c: re-add cond_resched() in shrink_dcache_parent()

On 14.04.2018 00:14, Andrew Morton wrote: > On Fri, 13 Apr 2018 13:28:23 -0700 Khazhismel Kumykov > wrote: > >> shrink_dcache_parent may spin waiting for a parallel shrink_dentry_list. >> In this case we may have 0 dentries to dispose, so we will never >> schedule out while waiting for the

Re: [PATCH] netfilter: CONFIG_NF_REJECT_IPV{4,6} becomes bool toggle

/Pablo-Neira-Ayuso/netfilter-CONFIG_NF_REJECT_IPV-4-6-becomes-bool-toggle/20180414-101337 base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 7.2.0 reproduce: wget https

Re: [PATCH] netfilter: CONFIG_NF_REJECT_IPV{4,6} becomes bool toggle

/Pablo-Neira-Ayuso/netfilter-CONFIG_NF_REJECT_IPV-4-6-becomes-bool-toggle/20180414-101337 base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 7.2.0 reproduce: wget https

Re: [PATCH 1/2] X86/KVM: Properly update 'tsc_offset' to represent the running guest

On Fri, 2018-04-13 at 17:35 +0200, Paolo Bonzini wrote: > On 13/04/2018 14:40, Raslan, KarimAllah wrote: > > > > > > > > > > > static void update_ia32_tsc_adjust_msr(struct kvm_vcpu *vcpu, s64 offset) > > > { > > > - u64 curr_offset = vcpu->arch.tsc_offset; > > > + u64 curr_offset =

Re: [PATCH 1/2] X86/KVM: Properly update 'tsc_offset' to represent the running guest

On Fri, 2018-04-13 at 17:35 +0200, Paolo Bonzini wrote: > On 13/04/2018 14:40, Raslan, KarimAllah wrote: > > > > > > > > > > > static void update_ia32_tsc_adjust_msr(struct kvm_vcpu *vcpu, s64 offset) > > > { > > > - u64 curr_offset = vcpu->arch.tsc_offset; > > > + u64 curr_offset =

Re: [PATCH 2/6] tracing: Add trace event error log

On Thu, 12 Apr 2018 18:52:13 -0500 Tom Zanussi wrote: > Hi Steve, > > On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote: > > On Thu, 12 Apr 2018 10:13:17 -0500 > > Tom Zanussi wrote: > > > > > diff --git a/kernel/trace/trace.h

Re: [PATCH 2/6] tracing: Add trace event error log

On Thu, 12 Apr 2018 18:52:13 -0500 Tom Zanussi wrote: > Hi Steve, > > On Thu, 2018-04-12 at 18:20 -0400, Steven Rostedt wrote: > > On Thu, 12 Apr 2018 10:13:17 -0500 > > Tom Zanussi wrote: > > > > > diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h > > > index 6fb46a0..f2dc7e6 100644 >

[PATCH] fs: avoid fdput() after failed fdget() in vfs_dedupe_file_range()

It's a fairly inconsequential bug, since fdput() won't actually try to fput() the file due to fd.flags (and thus FDPUT_FPUT) being zero in the failure case, but most other vfs code takes steps to avoid this. Signed-off-by: Zev Weiss --- fs/read_write.c | 6 +++--- 1 file

[PATCH] fs: avoid fdput() after failed fdget() in vfs_dedupe_file_range()

It's a fairly inconsequential bug, since fdput() won't actually try to fput() the file due to fd.flags (and thus FDPUT_FPUT) being zero in the failure case, but most other vfs code takes steps to avoid this. Signed-off-by: Zev Weiss --- fs/read_write.c | 6 +++--- 1 file changed, 3

Re: [PATCH] Documentation/i2c: sync docs with current state of i2c-tools.

> (also, did I send the v3 patch series threaded correctly?) Yes, that worked. Thanks! Things to improve there: I was both in To: and CC: field, so I got mails twice. Jean was missing completely. signature.asc Description: PGP signature

Re: [PATCH] Documentation/i2c: sync docs with current state of i2c-tools.

> (also, did I send the v3 patch series threaded correctly?) Yes, that worked. Thanks! Things to improve there: I was both in To: and CC: field, so I got mails twice. Jean was missing completely. signature.asc Description: PGP signature

<    1   2   3