IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+fef86971c84310f1c...@syzkaller.appspotmail.com
WARNING: lock held when returning to user space!
5.4.0-rc1 #0 Not tainted
a1360
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b825cd60
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+6b6a46cc150b19f54...@syzkaller.appspotmail.com
>
> =========
the bug, please add the following tag to the commit:
Reported-by: syzbot+6b6a46cc150b19f54...@syzkaller.appspotmail.com
WARNING: lock held when returning to user space!
5.4.0-rc1-next-20191001 #0 Not tainted
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
commit:
> > Reported-by: syzbot+6ea337c427f5083eb...@syzkaller.appspotmail.com
> >
> > RBP: 7ffe369ca7a0 R08: 0001 R09: 004009ce
> > R10: R11: 0246 R12: 0005
> > R13: ffffffff R14: 00000000 R15:
1 R09: 004009ce
> R10: R11: 0246 R12: 0005
> R13: R14: R15: 0000
>
> ========
> WARNING: lock held when returning to user space!
> 4.20.0+ #174 Not tainted
>
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,
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
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()
[ 1101.127520] WARNING: lock held when returning to user space!
[ 1101.133310] 4.20.0+ #396 Not tainted
[ 1101.137004]
[ 1101.142780] syz-executor0/29677 is leaving the kernel with locks still held!
[ 1101.149944] 1 lock held by syz-executor0/29677
+87b93137e0280beae...@syzkaller.appspotmail.com
WARNING: lock held when returning to user space!
4.20.0+ #396 Not tainted
syz-executor0/29677 is leaving the kernel with locks still held!
1 lock held by syz-executor0/29677:
#0: ec5f6915 (>s_umount_
53eabf40
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a492bf40
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+42e36e1ae3de3f22a...@syzkaller.appspotmail.com
#syz dup: WARNING: lock held when retur
R15:
WARNING: lock held when returning to user space!
4.20.0+ #395 Not tainted
syz-executor520/8085 is leaving the kernel with locks still held!
---
This bug is generated by a bot
R15:
WARNING: lock held when returning to user space!
4.20.0+ #174 Not tainted
syz-executor556/8153 is leaving the kernel with locks still held!
1 lock held by syz-executor556/8153
:
> >>> Reported-by: syzbot+3f7b29af1baa9d0a5...@syzkaller.appspotmail.com
> >>>
> >>> random: sshd: uninitialized urandom read (32 bytes read)
> >>> random: sshd: uninitialized urandom read (32 bytes read)
> >>> random: sshd: uniniti
:
> >>> Reported-by: syzbot+3f7b29af1baa9d0a5...@syzkaller.appspotmail.com
> >>>
> >>> random: sshd: uninitialized urandom read (32 bytes read)
> >>> random: sshd: uninitialized urandom read (32 bytes read)
> >>> random: sshd: uniniti
shd: uninitialized urandom read (32 bytes read)
>>> random: sshd: uninitialized urandom read (32 bytes read)
>>> random: sshd: uninitialized urandom read (32 bytes read)
>>>
>>>
>>> WARNING: lock held when returning to user space!
>>> 4.18
shd: uninitialized urandom read (32 bytes read)
>>> random: sshd: uninitialized urandom read (32 bytes read)
>>> random: sshd: uninitialized urandom read (32 bytes read)
>>>
>>>
>>> WARNING: lock held when returning to user space!
>>> 4.18
:
>> Reported-by: syzbot+3f7b29af1baa9d0a5...@syzkaller.appspotmail.com
>>
>> random: sshd: uninitialized urandom read (32 bytes read)
>> random: sshd: uninitialized urandom read (32 bytes read)
>> random: sshd: uninitialized urandom read (32 bytes read)
>>
>>
:
>> Reported-by: syzbot+3f7b29af1baa9d0a5...@syzkaller.appspotmail.com
>>
>> random: sshd: uninitialized urandom read (32 bytes read)
>> random: sshd: uninitialized urandom read (32 bytes read)
>> random: sshd: uninitialized urandom read (32 bytes read)
>>
>>
es read)
> random: sshd: uninitialized urandom read (32 bytes read)
> random: sshd: uninitialized urandom read (32 bytes read)
>
> ========
> WARNING: lock held when returning to user space!
> 4.18.0-rc4+ #143 Not tainted
> --
es read)
> random: sshd: uninitialized urandom read (32 bytes read)
> random: sshd: uninitialized urandom read (32 bytes read)
>
> ========
> WARNING: lock held when returning to user space!
> 4.18.0-rc4+ #143 Not tainted
> --
)
WARNING: lock held when returning to user space!
4.18.0-rc4+ #143 Not tainted
syz-executor012/4539 is leaving the kernel with locks still held!
1 lock held by syz-executor012/4539:
#0: (ptrval
)
WARNING: lock held when returning to user space!
4.18.0-rc4+ #143 Not tainted
syz-executor012/4539 is leaving the kernel with locks still held!
1 lock held by syz-executor012/4539:
#0: (ptrval
The patch was sent to linux.git as commit bdac616db9bbadb9.
#syz fix: loop: fix LOOP_GET_STATUS lock imbalance
The patch was sent to linux.git as commit bdac616db9bbadb9.
#syz fix: loop: fix LOOP_GET_STATUS lock imbalance
tag to the commit:
>>> Reported-by: syzbot+31e8daa8b3fc129e7...@syzkaller.appspotmail.com
>>> It will help syzbot understand when the bug is fixed. See footer for
>>> details.
>>> If you forward the report, please keep this part and the footer.
>>>
>>
gt;> Reported-by: syzbot+31e8daa8b3fc129e7...@syzkaller.appspotmail.com
>>> It will help syzbot understand when the bug is fixed. See footer for
>>> details.
>>> If you forward the report, please keep this part and the footer.
>>>
>>>
>>> =
l help syzbot understand when the bug is fixed. See footer for
>> details.
>> If you forward the report, please keep this part and the footer.
>>
>>
>>
>> WARNING: lock held when returning to user space!
>> 4.16.0+
syzbot understand when the bug is fixed. See footer for
>> details.
>> If you forward the report, please keep this part and the footer.
>>
>>
>>
>> WARNING: lock held when returning to user space!
>> 4.16.0+ #3 Not tainted
>> ---
bug, please add the following tag to the commit:
> Reported-by: syzbot+31e8daa8b3fc129e7...@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.
>
>
> ===
bug, please add the following tag to the commit:
> Reported-by: syzbot+31e8daa8b3fc129e7...@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.
>
>
> ===
understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
WARNING: lock held when returning to user space!
4.16.0+ #3 Not tainted
understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
WARNING: lock held when returning to user space!
4.16.0+ #3 Not tainted
34 matches
Mail list logo
