All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5df2d3fa14f2d3e49305@syzkaller.appspotmail.com>
To: jack@suse.com, jack@suse.cz, leocstone@gmail.com,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] WARNING in udf_rmdir (2)
Date: Tue, 14 Jan 2025 19:53:04 -0800	[thread overview]
Message-ID: <67873120.050a0220.20d369.0003.GAE@google.com> (raw)
In-Reply-To: <6747ce03.050a0220.253251.0066.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit c5566903af56dd1abb092f18dcb0c770d6cd8dcb
Author: Jan Kara <jack@suse.cz>
Date:   Tue Nov 26 11:46:00 2024 +0000

    udf: Skip parent dir link count update if corrupted

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12bc6a18580000
start commit:   228a1157fb9f Merge tag '6.13-rc-part1-SMB3-client-fixes' o..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=402159daa216c89d
dashboard link: https://syzkaller.appspot.com/bug?extid=5df2d3fa14f2d3e49305
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14b476e8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=162c0778580000

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

#syz fix: udf: Skip parent dir link count update if corrupted

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

  parent reply	other threads:[~2025-01-15  3:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  1:57 [syzbot] [udf?] WARNING in udf_rmdir (2) syzbot
2024-12-02  0:41 ` [PATCH] udf: Prevent rmdir of deleted directories Leo Stone
2024-12-02  1:01   ` [syzbot] [udf?] WARNING in udf_rmdir (2) syzbot
2024-12-02 12:28   ` [PATCH] udf: Prevent rmdir of deleted directories Jan Kara
2025-01-15  3:53 ` syzbot [this message]
2025-01-16 10:29   ` [syzbot] [udf?] WARNING in udf_rmdir (2) Jan Kara

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=67873120.050a0220.20d369.0003.GAE@google.com \
    --to=syzbot+5df2d3fa14f2d3e49305@syzkaller.appspotmail.com \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=leocstone@gmail.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.