From: syzbot <syzbot+82df44ede2faca24c729@syzkaller.appspotmail.com>
To: hdanton@sina.com, jack@suse.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
steve.magnani@digidescorp.com, steve@digidescorp.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] KASAN: use-after-free Read in udf_sync_fs
Date: Mon, 14 Aug 2023 13:07:34 -0700 [thread overview]
Message-ID: <000000000000f7d5180602e79cec@google.com> (raw)
In-Reply-To: <00000000000024d7f70602b705e9@google.com>
syzbot has bisected this issue to:
commit e8b4274735e416621cfb28c2802b4ad52da35d0f
Author: Steve Magnani <steve.magnani@digidescorp.com>
Date: Fri Feb 8 17:34:55 2019 +0000
udf: finalize integrity descriptor before writeback
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e3d76fa80000
start commit: f8de32cc060b Merge tag 'tpmdd-v6.5-rc7' of git://git.kerne..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16e3d76fa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=12e3d76fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=171b698bc2e613cf
dashboard link: https://syzkaller.appspot.com/bug?extid=82df44ede2faca24c729
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10df55d7a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e4d78ba80000
Reported-by: syzbot+82df44ede2faca24c729@syzkaller.appspotmail.com
Fixes: e8b4274735e4 ("udf: finalize integrity descriptor before writeback")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-14 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 10:09 [syzbot] [udf?] KASAN: use-after-free Read in udf_sync_fs syzbot
2023-08-14 20:07 ` syzbot [this message]
2024-02-01 0:18 ` syzbot
2024-02-01 9:14 ` 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=000000000000f7d5180602e79cec@google.com \
--to=syzbot+82df44ede2faca24c729@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve.magnani@digidescorp.com \
--cc=steve@digidescorp.com \
--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.