From: syzbot <syzbot+823cd0d24881f21ab9f1@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] WARNING in rcu_sync_dtor (2)
Date: Sat, 16 Nov 2024 16:46:03 -0800 [thread overview]
Message-ID: <67393ccb.050a0220.e1c64.000b.GAE@google.com> (raw)
In-Reply-To: <20241117002605.1398-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in rcu_sync_dtor
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6897 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
Modules linked in:
CPU: 0 UID: 0 PID: 6897 Comm: kworker/0:6 Not tainted 6.12.0-rc7-syzkaller-00212-g4a5df3796467-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Workqueue: events destroy_super_work
RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
Code: 74 19 e8 96 dd 00 00 43 0f b6 44 25 00 84 c0 0f 85 82 00 00 00 41 83 3f 00 75 1d 5b 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 90 <0f> 0b 90 e9 66 ff ff ff 90 0f 0b 90 eb 89 90 0f 0b 90 eb dd 44 89
RSP: 0018:ffffc9000368fb30 EFLAGS: 00010246
RAX: 0000000000000002 RBX: 1ffff1100c693c77 RCX: ffff88802b3dbc00
RDX: 0000000000000000 RSI: ffffffff8c6038c0 RDI: ffff88806349e350
RBP: 000000000000020f R08: ffffffff820f0544 R09: 1ffffffff1cfbc21
R10: dffffc0000000000 R11: fffffbfff1cfbc22 R12: dffffc0000000000
R13: 1ffff1100c693c6a R14: ffff88806349e350 R15: ffff88806349e350
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555a3b4608 CR3: 000000000e734000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42
destroy_super_work+0xef/0x130 fs/super.c:282
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Tested on:
commit: 4a5df379 Merge tag 'mm-hotfixes-stable-2024-11-16-15-3..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16cf9b5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b216897c3460507
dashboard link: https://syzkaller.appspot.com/bug?extid=823cd0d24881f21ab9f1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11207130580000
prev parent reply other threads:[~2024-11-17 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 9:33 syzbot
2024-11-16 23:09 ` Hillf Danton
2024-11-16 23:26 ` syzbot
2024-11-17 0:26 ` Hillf Danton
2024-11-17 0:46 ` syzbot [this message]
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=67393ccb.050a0220.e1c64.000b.GAE@google.com \
--to=syzbot+823cd0d24881f21ab9f1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®