mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+1ec0f904ba50d06110b1@syzkaller.appspotmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	edumazet@google.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in sys_umount (3)
Date: Tue, 19 Aug 2025 06:27:17 +0800	[thread overview]
Message-ID: <20250818222718.5061-1-hdanton@sina.com> (raw)
In-Reply-To: <20250818182616.GB222315@ZenIV>

On Mon, 18 Aug 2025 19:26:16 +0100 Al Viro wrote:
> On Mon, Aug 18, 2025 at 02:42:28AM -0700, syzbot wrote:
> > syzbot has found a reproducer for the following issue on:
> > 
> > HEAD commit:    8f5ae30d69d7 Linux 6.17-rc1
> > git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1321eba2580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
> > dashboard link: https://syzkaller.appspot.com/bug?extid=1ec0f904ba50d06110b1
> > compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> > userspace arch: arm64
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10cba442580000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10a1eba2580000
> > 
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/18a2e4bd0c4a/disk-8f5ae30d.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/3b5395881b25/vmlinux-8f5ae30d.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/e875f4e3b7ff/Image-8f5ae30d.gz.xz
> > mounted in repro: https://storage.googleapis.com/syzbot-assets/43186d9e448c/mount_0.gz
> >   fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=174ba442580000)
> > 
> > The issue was bisected to:
> > 
> > commit d15121be7485655129101f3960ae6add40204463
> > Author: Paolo Abeni <pabeni@redhat.com>
> > Date:   Mon May 8 06:17:44 2023 +0000
> > 
> >     Revert "softirq: Let ksoftirqd do its job"
> 
> Would be interesting to see how it behaves on 

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git  fixes

  reply	other threads:[~2025-08-18 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08  8:40 syzbot
2025-01-27 15:31 ` syzbot
2025-08-18  9:42 ` syzbot
2025-08-18 18:26   ` Al Viro
2025-08-18 22:27     ` Hillf Danton [this message]
2025-08-19  2: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=20250818222718.5061-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=edumazet@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+1ec0f904ba50d06110b1@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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®