From: syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Sat, 10 Dec 2022 18:30:22 -0800 [thread overview]
Message-ID: <00000000000025ff8d05ef842be6@google.com> (raw)
In-Reply-To: <20221211002908.2210-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in done_path_create
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88807217f1d0, owner = 0x0, curr 0xffff88807ce13a80, list empty
WARNING: CPU: 0 PID: 4220 at kernel/locking/rwsem.c:1361 __up_write kernel/locking/rwsem.c:1360 [inline]
WARNING: CPU: 0 PID: 4220 at kernel/locking/rwsem.c:1361 up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Modules linked in:
CPU: 0 PID: 4220 Comm: syz-executor.0 Not tainted 6.1.0-rc8-syzkaller-00152-g3ecc37918c80-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__up_write kernel/locking/rwsem.c:1360 [inline]
RIP: 0010:up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Code: c7 c0 a3 ed 8a 48 c7 c6 60 a6 ed 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 31 c0 53 e8 ab 7c e8 ff 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 58 4d 76 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90006d9fd20 EFLAGS: 00010292
RAX: 41e4cc6daa410d00 RBX: ffffffff8aeda4a0 RCX: ffff88807ce13a80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90006d9fdf8 R08: ffffffff816e5c7d R09: fffff52000db3f5d
R10: fffff52000db3f5d R11: 1ffff92000db3f5c R12: 0000000000000000
R13: ffff88807217f1d0 R14: 1ffff92000db3fac R15: dffffc0000000000
FS: 00007f3cd55fe700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b468143950 CR3: 0000000074553000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:762 [inline]
done_path_create+0xc4/0x150 fs/namei.c:3857
do_mkdirat+0x254/0x440 fs/namei.c:4064
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4074
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f3cde48c0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3cd55fe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f3cde5ac050 RCX: 00007f3cde48c0d9
RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000004
RBP: 00007f3cde4e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc1510851f R14: 00007f3cd55fe300 R15: 0000000000022000
</TASK>
Tested on:
commit: 3ecc3791 Merge tag 'media/v6.1-4' of git://git.kernel...
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=152559eb880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d58e7fe7f9cf5e24
dashboard link: https://syzkaller.appspot.com/bug?extid=919c5a9be8433b8bf201
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=14e9477d880000
next parent reply other threads:[~2022-12-11 2:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221211002908.2210-1-hdanton@sina.com>
2022-12-11 2:30 ` syzbot [this message]
2022-12-11 2:52 ` [syzbot] WARNING in do_mkdirat Al Viro
2022-12-11 7:56 ` Hillf Danton
2022-12-11 8:39 ` Al Viro
2022-12-11 10:22 ` Hillf Danton
2022-12-11 15:46 ` Matthew Wilcox
2022-12-11 20:54 ` Al Viro
2022-12-12 3:29 ` Hillf Danton
2022-12-12 18:58 ` Theodore Ts'o
2022-12-12 19:29 ` Marco Elver
2022-12-13 1:44 ` Al Viro
2022-12-13 2:25 ` Hillf Danton
2022-12-16 15:48 ` Aleksandr Nogikh
2022-12-29 21:17 ` Eric Biggers
2022-12-31 16:57 ` Theodore Ts'o
2022-12-31 17:03 ` Randy Dunlap
2023-01-03 13:36 ` Aleksandr Nogikh
2022-12-13 1:47 ` Hillf Danton
2022-12-13 3:36 ` Al Viro
2022-12-13 4:12 ` Hillf Danton
2022-12-13 11:05 ` Alexander Potapenko
[not found] <20221215235133.1097-1-hdanton@sina.com>
2022-12-16 7:53 ` syzbot
[not found] <20221210011440.2050-1-hdanton@sina.com>
2022-12-10 7:24 ` syzbot
2022-12-03 14:52 syzbot
2022-12-04 1:04 ` Hillf Danton
2022-12-09 19:50 ` syzbot
2022-12-09 19:57 ` Matthew Wilcox
2022-12-10 18:06 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000025ff8d05ef842be6@google.com \
--to=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.