All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a41b73dce23962a74c72@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	 linux-usb@vger.kernel.org, ssranevjti@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] [usb?] memory leak in v4l2_ctrl_handler_init_class (2)
Date: Tue, 25 Nov 2025 13:09:02 -0800	[thread overview]
Message-ID: <69261aee.a70a0220.2ea503.0092.GAE@google.com> (raw)
In-Reply-To: <ca9d89ca-4da9-4f2b-bd92-3791cae54911@gmail.com>

Hello,

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

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

Tested on:

commit:         30f09200 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17d5cf42580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44
dashboard link: https://syzkaller.appspot.com/bug?extid=a41b73dce23962a74c72
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=164ea612580000

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

  reply	other threads:[~2025-11-25 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  7:55 [syzbot] [media?] [usb?] memory leak in v4l2_ctrl_handler_init_class (2) syzbot
2025-11-25 17:01 ` shaurya
2025-11-25 20:38   ` syzbot
2025-11-25 17:03 ` shaurya
2025-11-25 21:09   ` syzbot [this message]
2025-11-25 20:21 ` shaurya
2025-11-25 21:29   ` 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=69261aee.a70a0220.2ea503.0092.GAE@google.com \
    --to=syzbot+a41b73dce23962a74c72@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ssranevjti@gmail.com \
    --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.