All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3f395d8da879a58fb019@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] INFO: trying to register non-static key in as102_dvb_dmx_start_feed
Date: Thu, 26 Mar 2026 05:40:02 -0700	[thread overview]
Message-ID: <69c52922.050a0220.330c49.0002.GAE@google.com> (raw)
In-Reply-To: <tencent_E72577BA88BBC133769EDE1B8E4BFE1B7F08@qq.com>

Hello,

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

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

Tested on:

commit:         0138af24 Merge tag 'erofs-for-7.0-rc6-fixes' of git://..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167c8eda580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=45cb3c58fd963c27
dashboard link: https://syzkaller.appspot.com/bug?extid=3f395d8da879a58fb019
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10591cba580000

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

  reply	other threads:[~2026-03-26 12:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  5:13 [syzbot] [media?] INFO: trying to register non-static key in as102_dvb_dmx_start_feed syzbot
2026-03-26  9:29 ` Edward Adam Davis
2026-03-26 10:12   ` syzbot
2026-03-26 11:13 ` Edward Adam Davis
2026-03-26 11:44   ` syzbot
2026-03-26 12:15 ` Edward Adam Davis
2026-03-26 12:40   ` syzbot [this message]
2026-03-26 12:45 ` Edward Adam Davis
2026-03-26 13:12   ` syzbot
2026-03-26 13:17 ` [PATCH] media: usb: as102: fix race condition between ioctl and register Edward Adam Davis
2026-06-02 15:55   ` [PATCH] media: usb: as102: initialize mutexes before registration Joel Peech
2026-06-02 16:08     ` sashiko-bot

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=69c52922.050a0220.330c49.0002.GAE@google.com \
    --to=syzbot+3f395d8da879a58fb019@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.