Re: WARNING: lock held when returning to user space in membarrier_private_expedited

2019-10-01 Thread Peter Zijlstra
On Tue, Oct 01, 2019 at 01:09:07AM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:afb37288 Add linux-next specific files for 20191001 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=1761963560 > kernel config

Re: WARNING: lock held when returning to user space in set_property_atomic

2019-01-04 Thread Tetsuo Handa
On 2019/01/03 18:04, Dmitry Vyukov wrote: > On Thu, Jan 3, 2019 at 9:55 AM Maarten Lankhorst > wrote: >> Just guessing.. >> >> Does this help? Yes it will. And while at it, let's fix another one together. >From 291e42211e3cc6d85c915772717dd08d40fb5fed Mon Sep 17 00:00:00 2001 From: Tetsuo Handa

Re: WARNING: lock held when returning to user space in set_property_atomic

2019-01-03 Thread Dmitry Vyukov
On Thu, Jan 3, 2019 at 9:55 AM Maarten Lankhorst wrote: > > Op 30-12-2018 om 07:21 schreef syzbot: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/.. > > git tree: upstream > > console output: https://s

Re: WARNING: lock held when returning to user space in set_property_atomic

2019-01-03 Thread Maarten Lankhorst
Op 30-12-2018 om 07:21 schreef syzbot: > Hello, > > syzbot found the following crash on: > > HEAD commit:    903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/.. > git tree:   upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=12d0f55340 > kernel config:  https://s

Re: WARNING: lock held when returning to user space in grab_super

2019-01-02 Thread Tejun Heo
On Thu, Jan 03, 2019 at 01:49:55AM +0900, Tetsuo Handa wrote: > kernfs_node_dentry() calls lookup_one_len_unlocked() which involves > memory allocation, and memory allocation fault injection made > lookup_one_len_unlocked() fail, and thus kernfs_node_dentry() failed. > What's strange? So, kernfs_n

Re: WARNING: lock held when returning to user space in grab_super

2019-01-02 Thread Tetsuo Handa
On 2019/01/03 1:16, Tejun Heo wrote: > Happy new year, Tetsuo. > > On Wed, Jan 02, 2019 at 09:08:56PM +0900, Tetsuo Handa wrote: >> According to commit 633feee310de6b6c ("cgroup: refactor mount path and >> clearly distinguish v1 and v2 paths"), cgroup_do_mount() is failing to >> do full teardown s

Re: WARNING: lock held when returning to user space in grab_super

2019-01-02 Thread Tejun Heo
Happy new year, Tetsuo. On Wed, Jan 02, 2019 at 09:08:56PM +0900, Tetsuo Handa wrote: > According to commit 633feee310de6b6c ("cgroup: refactor mount path and > clearly distinguish v1 and v2 paths"), cgroup_do_mount() is failing to > do full teardown steps for kernfs_mount() (deactivate_locked_sup

Re: WARNING: lock held when returning to user space in grab_super

2019-01-02 Thread Tetsuo Handa
Hello, Tejun. [ 1100.561812] FAULT_INJECTION: forcing a failure. [ 1100.561812] name failslab, interval 1, probability 0, space 0, times 0 [ 1100.625231] CPU: 1 PID: 29677 Comm: syz-executor0 Not tainted 4.20.0+ #396 [ 1100.632289] Hardware name: Google Google Compute Engine/Google Compute Engine

Re: WARNING: lock held when returning to user space! (3)

2019-01-02 Thread Dmitry Vyukov
On Wed, Jan 2, 2019 at 11:59 AM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1424673b40 > kernel config:

Re: WARNING: lock held when returning to user space in fuse_lock_inode

2018-07-17 Thread Alistair Strachan
On Tue, Jul 17, 2018 at 5:46 AM Miklos Szeredi wrote: > On Tue, Jul 17, 2018 at 1:36 PM, Dmitry Vyukov wrote: > > On Tue, Jul 17, 2018 at 1:14 PM, Miklos Szeredi wrote: > >> On Thu, Jul 12, 2018 at 5:49 PM, syzbot > >> wrote: > >>> Hello, > >>> > >>> syzbot found the following crash on: > >>> >

Re: WARNING: lock held when returning to user space in fuse_lock_inode

2018-07-17 Thread Miklos Szeredi
On Tue, Jul 17, 2018 at 1:36 PM, Dmitry Vyukov wrote: > On Tue, Jul 17, 2018 at 1:14 PM, Miklos Szeredi wrote: >> On Thu, Jul 12, 2018 at 5:49 PM, syzbot >> wrote: >>> Hello, >>> >>> syzbot found the following crash on: >>> >>> HEAD commit:c25c74b7476e Merge tag 'trace-v4.18-rc3-2' of git://

Re: WARNING: lock held when returning to user space in fuse_lock_inode

2018-07-17 Thread Dmitry Vyukov
On Tue, Jul 17, 2018 at 1:14 PM, Miklos Szeredi wrote: > On Thu, Jul 12, 2018 at 5:49 PM, syzbot > wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:c25c74b7476e Merge tag 'trace-v4.18-rc3-2' of git://git.ke.. >> git tree: upstream >> console output: https://

Re: WARNING: lock held when returning to user space in fuse_lock_inode

2018-07-17 Thread Miklos Szeredi
On Thu, Jul 12, 2018 at 5:49 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c25c74b7476e Merge tag 'trace-v4.18-rc3-2' of git://git.ke.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=177bcec240 > kernel config:

Re: WARNING: lock held when returning to user space!

2018-04-14 Thread Tetsuo Handa
The patch was sent to linux.git as commit bdac616db9bbadb9. #syz fix: loop: fix LOOP_GET_STATUS lock imbalance

Re: WARNING: lock held when returning to user space!

2018-04-06 Thread Jens Axboe
On 4/6/18 8:57 AM, Dmitry Vyukov wrote: > On Fri, Apr 6, 2018 at 4:27 PM, Jens Axboe wrote: >> On 4/6/18 7:02 AM, syzbot wrote: >>> Hello, >>> >>> syzbot hit the following crash on upstream commit >>> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) >>> Merge tag 'armsoc-dr

Re: WARNING: lock held when returning to user space!

2018-04-06 Thread Dmitry Vyukov
On Fri, Apr 6, 2018 at 4:27 PM, Jens Axboe wrote: > On 4/6/18 7:02 AM, syzbot wrote: >> Hello, >> >> syzbot hit the following crash on upstream commit >> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) >> Merge tag 'armsoc-drivers' of >> git://git.kernel.org/pub/scm/linux/

Re: WARNING: lock held when returning to user space!

2018-04-06 Thread Jens Axboe
On 4/6/18 7:02 AM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) > Merge tag 'armsoc-drivers' of > git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc > syzbot dashboard link: > http