All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bc1aabf52d0a31e91f96@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] KASAN: slab-out-of-bounds Read in ieee80211_add_virtual_monitor
Date: Thu, 04 Dec 2025 07:30:02 -0800	[thread overview]
Message-ID: <6931a8fa.a70a0220.d98e3.01d5.GAE@google.com> (raw)
In-Reply-To: <b0ff5a33311bffd6f18f941968dd78fb3170f9a1.camel@yandex.ru>

Hello,

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

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

Tested on:

commit:         bc04acf4 Add linux-next specific files for 20251204
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=10283192580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b9f785244b836412
dashboard link: https://syzkaller.appspot.com/bug?extid=bc1aabf52d0a31e91f96
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=119cc01a580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-12-04 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b0ff5a33311bffd6f18f941968dd78fb3170f9a1.camel@yandex.ru>
2025-12-04 15:30 ` syzbot [this message]
     [not found] <82b033a0697247a7717c9a74831f88b4af1532a1.camel@yandex.ru>
2025-12-04 14:32 ` [syzbot] [wireless?] KASAN: slab-out-of-bounds Read in ieee80211_add_virtual_monitor syzbot
     [not found] <a070ad887e83969f83c8e8ce805e30b262a832fb.camel@yandex.ru>
2025-12-04 13:55 ` syzbot
2025-11-16  7:50 syzbot
2025-11-28 15:04 ` 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=6931a8fa.a70a0220.d98e3.01d5.GAE@google.com \
    --to=syzbot+bc1aabf52d0a31e91f96@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --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.