From: syzbot <syzbot+05d7520be047c9be86e0@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text
Date: Mon, 29 Jul 2024 20:03:03 -0700 [thread overview]
Message-ID: <00000000000054f2ec061e6e379f@google.com> (raw)
In-Reply-To: <tencent_DAEC5ACEE079366E9C2C516E6C9568E9AA0A@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+05d7520be047c9be86e0@syzkaller.appspotmail.com
Tested-by: syzbot+05d7520be047c9be86e0@syzkaller.appspotmail.com
Tested on:
commit: 1722389b Merge tag 'net-6.11-rc1' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=155741c9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b698a1b2fcd7ef5f
dashboard link: https://syzkaller.appspot.com/bug?extid=05d7520be047c9be86e0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1492a303980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-07-30 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
2024-07-30 2:17 ` Edward Adam Davis
2024-07-30 3:03 ` syzbot [this message]
2024-07-30 4:10 ` [PATCH] bcachefs: Add checks for entry's _data bytes Edward Adam Davis
2024-07-31 0:52 ` Kent Overstreet
2024-07-31 1:35 ` [PATCH V2] " Edward Adam Davis
2024-07-31 1:41 ` [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text Edward Adam Davis
2024-07-31 2:04 ` syzbot
2024-11-11 21:03 ` [syzbot] 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=00000000000054f2ec061e6e379f@google.com \
--to=syzbot+05d7520be047c9be86e0@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 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.