From: syzbot <syzbot+2bf29e42be0666f2df70@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] KASAN: slab-use-after-free Write in media_request_alloc
Date: Fri, 02 Jan 2026 03:55:02 -0800 [thread overview]
Message-ID: <6957b216.050a0220.a1b6.0362.GAE@google.com> (raw)
In-Reply-To: <20e6d0eef04a814e4b377b536f03e70565f492ac.camel@yandex.ru>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2bf29e42be0666f2df70@syzkaller.appspotmail.com
Tested-by: syzbot+2bf29e42be0666f2df70@syzkaller.appspotmail.com
Tested on:
commit: b69053dd wifi: mt76: Remove blank line after mt792x fi..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14dcbfb4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=513255d80ab78f2b
dashboard link: https://syzkaller.appspot.com/bug?extid=2bf29e42be0666f2df70
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=15ccbfb4580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-01-02 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20e6d0eef04a814e4b377b536f03e70565f492ac.camel@yandex.ru>
2026-01-02 11:55 ` syzbot [this message]
[not found] <69a08273.a70a0220.1e4086.5f64SMTPIN_ADDED_MISSING@gmr-mx.google.com>
2026-02-26 17:48 ` [syzbot] [media?] KASAN: slab-use-after-free Write in media_request_alloc syzbot
[not found] <69a06176.050a0220.18f3f1.5d0dSMTPIN_ADDED_MISSING@gmr-mx.google.com>
2026-02-26 15:43 ` syzbot
2026-01-02 3:38 syzbot
2026-01-02 4:23 ` Hillf Danton
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=6957b216.050a0220.a1b6.0362.GAE@google.com \
--to=syzbot+2bf29e42be0666f2df70@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox