From: syzbot <syzbot+c0360e8367d6d8d04a66@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in vfs_get_tree
Date: Wed, 25 Sep 2024 06:26:04 -0700 [thread overview]
Message-ID: <66f40f6c.050a0220.211276.0030.GAE@google.com> (raw)
In-Reply-To: <tencent_E8477769977226C7D37D8373E975C3AD0405@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c0360e8367d6d8d04a66@syzkaller.appspotmail.com
Tested-by: syzbot+c0360e8367d6d8d04a66@syzkaller.appspotmail.com
Tested on:
commit: 684a64bf Merge tag 'nfs-for-6.12-1' of git://git.linux..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167b4a80580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd75e1a00004094f
dashboard link: https://syzkaller.appspot.com/bug?extid=c0360e8367d6d8d04a66
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13b332a9980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-09-25 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 21:35 [syzbot] [bcachefs?] [jfs?] kernel BUG in vfs_get_tree syzbot
2024-09-24 22:18 ` [syzbot] [bcachefs?] " syzbot
2024-09-25 0:23 ` Edward Adam Davis
2024-09-25 0:41 ` syzbot
2024-09-25 1:26 ` Edward Adam Davis
2024-09-25 1:42 ` syzbot
2024-09-25 12:09 ` Edward Adam Davis
2024-09-25 12:26 ` syzbot
2024-09-25 12:42 ` Edward Adam Davis
2024-09-25 12:53 ` syzbot
2024-09-25 13:01 ` Edward Adam Davis
2024-09-25 13:26 ` syzbot [this message]
2024-09-25 13:53 ` [PATCH] bcachefs: return the error code instead of the return value of IS_ERR_OR_NULL Edward Adam Davis
2024-09-25 15:20 ` Kent Overstreet
2024-09-25 7:24 ` [syzbot] [bcachefs?] kernel BUG in vfs_get_tree syzbot
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=66f40f6c.050a0220.211276.0030.GAE@google.com \
--to=syzbot+c0360e8367d6d8d04a66@syzkaller.appspotmail.com \
--cc=eadavis@qq.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