From: syzbot <syzbot+93cbdd0ab421adc5275d@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: [syzbot] WARNING in kernfs_remove_by_name_ns (3)
Date: Wed, 29 Dec 2021 11:50:29 -0800 [thread overview]
Message-ID: <000000000000f927de05d44e3f30@google.com> (raw)
In-Reply-To: <00000000000047624505d0453c58@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: e7c124bd0463 Merge tag 'selinux-pr-20211228' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=160bdec3b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ebd4b29568807bc
dashboard link: https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f5025db00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1009b371b00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+93cbdd0ab421adc5275d@syzkaller.appspotmail.com
WARNING: CPU: 1 PID: 4574 at fs/kernfs/dir.c:1536 kernfs_remove_by_name_ns+0x61/0x90 fs/kernfs/dir.c:1535
Modules linked in:
CPU: 1 PID: 4574 Comm: syz-executor510 Not tainted 5.16.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:kernfs_remove_by_name_ns+0x61/0x90 fs/kernfs/dir.c:1535
Code: 48 89 c3 e8 e1 5f 7d ff 48 89 df e8 c9 e7 ff ff 31 db eb 29 e8 d0 5f 7d ff 48 c7 c7 00 95 83 8a 4c 89 fe 31 c0 e8 9f 46 47 ff <0f> 0b bb fe ff ff ff eb 16 e8 b1 5f 7d ff bb fe ff ff ff 48 c7 c7
RSP: 0018:ffffc900049779f0 EFLAGS: 00010246
RAX: 50855e28c77b3200 RBX: 0000000000000000 RCX: ffff888077b0d700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffffffff15a67d0 R08: ffffffff816a1042 R09: ffffed10173667b1
R10: ffffed10173667b1 R11: 0000000000000000 R12: ffffffff8d112008
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffffff8ad33ee0
FS: 00007f9f18971700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9f1894fec8 CR3: 0000000014b98000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kernfs_remove_by_name include/linux/kernfs.h:570 [inline]
remove_files fs/sysfs/group.c:28 [inline]
sysfs_remove_group+0xf7/0x280 fs/sysfs/group.c:288
sysfs_remove_groups+0x5b/0xb0 fs/sysfs/group.c:312
__kobject_del+0x84/0x310 lib/kobject.c:611
kobject_del+0x41/0x60 lib/kobject.c:643
blk_mq_unregister_hctx block/blk-mq-sysfs.c:183 [inline]
blk_mq_sysfs_unregister+0x215/0x300 block/blk-mq-sysfs.c:302
__blk_mq_update_nr_hw_queues block/blk-mq.c:4196 [inline]
blk_mq_update_nr_hw_queues+0x607/0x1250 block/blk-mq.c:4241
nbd_start_device+0x176/0xcb0 drivers/block/nbd.c:1347
nbd_start_device_ioctl drivers/block/nbd.c:1397 [inline]
__nbd_ioctl drivers/block/nbd.c:1471 [inline]
nbd_ioctl+0x30f/0xb80 drivers/block/nbd.c:1511
blkdev_ioctl+0x3ac/0x790 block/ioctl.c:609
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f9f189c4379
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 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:00007f9f189712e8 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f9f18a484e0 RCX: 00007f9f189c4379
RDX: 0000000000000000 RSI: 000000000000ab03 RDI: 0000000000000006
RBP: 00007f9f18a15194 R08: 0000000000000001 R09: 0000000000000035
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9f18a484ec
R13: 00007f9f189712f0 R14: 00007f9f18a484e8 R15: 0000000000000001
</TASK>
next prev parent reply other threads:[~2021-12-29 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 11:24 [syzbot] WARNING in kernfs_remove_by_name_ns (3) syzbot
2021-12-29 19:50 ` syzbot [this message]
2024-05-15 16:29 ` David Sterba
2024-05-15 19:08 ` Tejun Heo
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=000000000000f927de05d44e3f30@google.com \
--to=syzbot+93cbdd0ab421adc5275d@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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.