From: syzbot <syzbot+56fbf4c7ddf65e95c7cc@syzkaller.appspotmail.com>
To: eslam.medhat1993@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nbd?] KASAN: slab-use-after-free Write in recv_work (3)
Date: Wed, 05 Nov 2025 07:13:04 -0800 [thread overview]
Message-ID: <690b6980.050a0220.3d0d33.0053.GAE@google.com> (raw)
In-Reply-To: <9f0a89ac-f782-4afb-8fe5-9575de76b201@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+56fbf4c7ddf65e95c7cc@syzkaller.appspotmail.com
Tested-by: syzbot+56fbf4c7ddf65e95c7cc@syzkaller.appspotmail.com
Tested on:
commit: 84d39fb9 Add linux-next specific files for 20251105
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15cd1342580000
kernel config: https://syzkaller.appspot.com/x/.config?x=413cf24e78b667b9
dashboard link: https://syzkaller.appspot.com/bug?extid=56fbf4c7ddf65e95c7cc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=15fc2012580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-05 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f0a89ac-f782-4afb-8fe5-9575de76b201@gmail.com>
2025-11-05 15:13 ` syzbot [this message]
[not found] <20251107011853.3653104-1-lizhi.xu@windriver.com>
2025-11-07 3:13 ` [syzbot] [nbd?] KASAN: slab-use-after-free Write in recv_work (3) syzbot
[not found] <20251103064432.3767881-1-lizhi.xu@windriver.com>
2025-11-03 6:53 ` syzbot
[not found] <20251103054919.3377129-1-lizhi.xu@windriver.com>
2025-11-03 6:25 ` syzbot
[not found] <20251103021018.2052011-1-lizhi.xu@windriver.com>
2025-11-03 2:52 ` syzbot
2025-11-02 23:48 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=690b6980.050a0220.3d0d33.0053.GAE@google.com \
--to=syzbot+56fbf4c7ddf65e95c7cc@syzkaller.appspotmail.com \
--cc=eslam.medhat1993@gmail.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