From: syzbot <syzbot+2faac0423fdc9692822b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] KASAN: slab-use-after-free Read in test_bdev_super_fc
Date: Fri, 04 Aug 2023 17:11:26 -0700 [thread overview]
Message-ID: <000000000000b08a42060221da36@google.com> (raw)
In-Reply-To: <20230804233428.1642-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+2faac0423fdc9692822b@syzkaller.appspotmail.com
Tested on:
commit: d7b3af5a Add linux-next specific files for 20230728
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=127ac313a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=62dd327c382e3fe
dashboard link: https://syzkaller.appspot.com/bug?extid=2faac0423fdc9692822b
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=146c855da80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-08-05 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230804233428.1642-1-hdanton@sina.com>
2023-08-05 0:11 ` syzbot [this message]
[not found] <20230804125406.1583-1-hdanton@sina.com>
2023-08-04 19:13 ` [syzbot] [fs?] KASAN: slab-use-after-free Read in test_bdev_super_fc syzbot
2023-08-03 22:14 syzbot
2023-08-04 10:14 ` Christoph Hellwig
2023-08-04 13:20 ` Christian Brauner
2023-08-04 14:02 ` Christoph Hellwig
2023-08-04 14:36 ` Christian Brauner
2023-08-04 14:43 ` Christoph Hellwig
2023-08-04 14:49 ` Christian Brauner
2023-08-04 15:29 ` Christian Brauner
2023-08-05 8:57 ` Christoph Hellwig
[not found] ` <20230805084316.1699-1-hdanton@sina.com>
2023-08-05 8:48 ` Christoph Hellwig
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=000000000000b08a42060221da36@google.com \
--to=syzbot+2faac0423fdc9692822b@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).