From: syzbot <syzbot+f25c61df1ec3d235d52f@syzkaller.appspotmail.com>
To: brauner@kernel.org
Cc: brauner@kernel.org, gregkh@linuxfoundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: [syzbot] [kernfs?] KASAN: slab-use-after-free Read in kernfs_test_super
Date: Mon, 28 Aug 2023 02:20:43 -0700 [thread overview]
Message-ID: <0000000000007459b80603f83591@google.com> (raw)
In-Reply-To: <20230828-schande-hungrig-b2a6ebffb5f6@brauner>
> #syz dup: [syzbot] [fuse?] KASAN: slab-use-after-free Read in fuse_test_super
can't find the dup bug
next prev parent reply other threads:[~2023-08-28 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 16:53 [syzbot] [kernfs?] KASAN: slab-use-after-free Read in kernfs_test_super syzbot
2023-08-28 9:20 ` Christian Brauner
2023-08-28 9:20 ` syzbot [this message]
2023-08-28 9:22 ` Christian Brauner
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=0000000000007459b80603f83591@google.com \
--to=syzbot+f25c61df1ec3d235d52f@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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 NNTP newsgroup(s).