All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+42986aeeddfd7ed93c8b@syzkaller.appspotmail.com>
To: brauner@kernel.org, hdanton@sina.com, jack@suse.cz,
	linkinjeon@kernel.org,  linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	sj1557.seo@samsung.com,  syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk,  yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat] INFO: task hung in vfs_rmdir (2)
Date: Tue, 07 Oct 2025 22:52:03 -0700	[thread overview]
Message-ID: <68e5fc03.a00a0220.298cc0.0488.GAE@google.com> (raw)
In-Reply-To: <00000000000054d8540619f43b86@google.com>

syzbot suspects this issue was fixed by commit:

commit 79c1587b6cda74deb0c86fc7ba194b92958c793c
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Sat Aug 30 05:44:35 2025 +0000

    exfat: validate cluster allocation bits of the allocation bitmap

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1695f92f980000
start commit:   4a4be1ad3a6e Revert "vfs: Delete the associated dentry whe..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=47d282ddffae809f
dashboard link: https://syzkaller.appspot.com/bug?extid=42986aeeddfd7ed93c8b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12a5b3ec980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=103820f2980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: exfat: validate cluster allocation bits of the allocation bitmap

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-10-08  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  3:50 [syzbot] [ext4?] INFO: task hung in vfs_rmdir (2) syzbot
2024-06-03  3:56 ` Al Viro
2024-06-03  4:14   ` syzbot
2024-06-03  4:21   ` Al Viro
2024-06-03  4:22     ` Al Viro
2024-06-03  4:34     ` syzbot
2024-06-03 10:42 ` Hillf Danton
2024-06-03 11:08   ` syzbot
2024-06-03 11:27 ` Jan Kara
2025-10-08  5:52 ` 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=68e5fc03.a00a0220.298cc0.0488.GAE@google.com \
    --to=syzbot+42986aeeddfd7ed93c8b@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=linkinjeon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yuezhang.mo@sony.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.