From: syzbot <syzbot+de2fef01040748da6822@syzkaller.appspotmail.com>
To: golasch18@web.de, jack@suse.com, jack@suse.cz,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] WARNING in udf_map_block
Date: Tue, 27 Oct 2026 08:56:02 -0700 [thread overview]
Message-ID: <6ae0c992.768774f5.3237ab.0019.GAE@google.com> (raw)
In-Reply-To: <6a81cb33.9ebadd4d.20b15e.0018.GAE@google.com>
syzbot has bisected this issue to:
commit 62333e480d12ab186f89fe2725b372d12f72d5eb
Author: Jan Kara <jack@suse.cz>
Date: Thu Jul 30 10:42:29 2026 +0000
udf: Fix data loss when converting inline inodes to out of line
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1422482d580000
start commit: d135ab453a74 Merge tag 'backlight-next-7.4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1622482d580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1222482d580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b990d88b41ee3220
dashboard link: https://syzkaller.appspot.com/bug?extid=de2fef01040748da6822
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c93721580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16146469580000
Reported-by: syzbot+de2fef01040748da6822@syzkaller.appspotmail.com
Fixes: 62333e480d12 ("udf: Fix data loss when converting inline inodes to out of line")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-10-27 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 14:37 [syzbot] [udf?] WARNING in udf_map_block syzbot
2026-10-27 6:16 ` syzbot
2026-10-27 15:56 ` 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=6ae0c992.768774f5.3237ab.0019.GAE@google.com \
--to=syzbot+de2fef01040748da6822@syzkaller.appspotmail.com \
--cc=golasch18@web.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--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.