From: syzbot <syzbot+4cb1e27475bf90a9b926@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, cmaiolino@redhat.com,
lczerner@redhat.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, sjc@chobot.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
wanjiabing@vivo.com
Subject: Re: [syzbot] KASAN: use-after-free Read in ext4_xattr_set_entry (4)
Date: Wed, 23 Mar 2022 08:07:15 -0700 [thread overview]
Message-ID: <000000000000b8cdba05dae41558@google.com> (raw)
In-Reply-To: <00000000000079c56a05ba1c18c3@google.com>
syzbot suspects this issue was fixed by commit:
commit 6e47a3cc68fc525428297a00524833361ebbb0e9
Author: Lukas Czerner <lczerner@redhat.com>
Date: Wed Oct 27 14:18:52 2021 +0000
ext4: get rid of super block and sbi from handle_mount_ops()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100bc10b700000
start commit: f8ad8187c3b5 fs/pipe: allow sendfile() to pipe again
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=96b123631a6700e9
dashboard link: https://syzkaller.appspot.com/bug?extid=4cb1e27475bf90a9b926
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11131f94d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c3761b500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: get rid of super block and sbi from handle_mount_ops()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-03-23 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 11:05 KASAN: use-after-free Read in ext4_xattr_set_entry (4) syzbot
2022-03-23 15:07 ` syzbot [this message]
2022-03-25 6:18 ` [syzbot] " Dmitry Vyukov
2022-03-29 11:50 ` Ritesh Harjani
2022-03-29 12:01 ` Dmitry Vyukov
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=000000000000b8cdba05dae41558@google.com \
--to=syzbot+4cb1e27475bf90a9b926@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=cmaiolino@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjc@chobot.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=wanjiabing@vivo.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.