From: syzbot <syzbot+f25c61df1ec3d235d52f@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernfs?] KASAN: slab-use-after-free Read in kernfs_test_super
Date: Sun, 27 Aug 2023 06:19:28 -0700 [thread overview]
Message-ID: <00000000000071802f0603e76d83@google.com> (raw)
In-Reply-To: <20230827123619.3750-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+f25c61df1ec3d235d52f@syzkaller.appspotmail.com
Tested on:
commit: 28c736b0 Add linux-next specific files for 20230822
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=13e2b3bba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=20999f779fa96017
dashboard link: https://syzkaller.appspot.com/bug?extid=f25c61df1ec3d235d52f
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=1362b3bba80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-08-27 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230827123619.3750-1-hdanton@sina.com>
2023-08-27 13:19 ` syzbot [this message]
[not found] <20230827100849.3681-1-hdanton@sina.com>
2023-08-27 11:04 ` [syzbot] [kernfs?] KASAN: slab-use-after-free Read in kernfs_test_super syzbot
[not found] <20230827044001.3605-1-hdanton@sina.com>
2023-08-27 5:30 ` syzbot
[not found] <20230827020301.3530-1-hdanton@sina.com>
2023-08-27 3:15 ` syzbot
2023-08-26 16:53 syzbot
2023-08-28 9:20 ` Christian Brauner
2023-08-28 9:20 ` syzbot
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=00000000000071802f0603e76d83@google.com \
--to=syzbot+f25c61df1ec3d235d52f@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 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.