public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list
Date: Tue, 10 Dec 2024 03:28:02 -0800	[thread overview]
Message-ID: <675825c2.050a0220.2477f.0061.GAE@google.com> (raw)
In-Reply-To: <tencent_E4D7465C09A9AEDF6EEE4C9AA7C386F1D206@qq.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com
Tested-by: syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com

Tested on:

commit:         6ddd5d53 ocfs2: Take the smaller of l_next_free_rec an..
git tree:       https://github.com/ea1davis/linux ocfs2/syz
console output: https://syzkaller.appspot.com/x/log.txt?x=145d7c0f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=82d76f5a1a8b5c36
dashboard link: https://syzkaller.appspot.com/bug?extid=2313dda4dc4885c93578
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-12-10 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 23:04 [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list syzbot
2024-12-10 11:02 ` Edward Adam Davis
2024-12-10 11:28   ` syzbot [this message]
2024-12-10 11:23 ` Julian Sun
2024-12-10 11:47   ` syzbot
2024-12-10 11:27 ` [syzbot] Re: KASAN: use-after-free Read in ocfs2_search_extent_list() syzbot
     [not found] <20241210112732.8xyF9%dmantipov@yandex.ru>
2024-12-10 12:06 ` [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list 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=675825c2.050a0220.2477f.0061.GAE@google.com \
    --to=syzbot+2313dda4dc4885c93578@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