All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com>
To: benjamin.gaignard@collabora.com, daniel.almeida@collabora.com,
	 hdanton@sina.com, hverkuil-cisco@xs4all.nl,
	laurent.pinchart@ideasonboard.com,  linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org, mchehab@kernel.org,
	 nicolas.dufresne@collabora.com, sakari.ailus@linux.intel.com,
	 syzkaller-bugs@googlegroups.com, umang.jain@ideasonboard.com
Subject: Re: [syzbot] [media?] possible deadlock in v4l2_ctrl_handler_log_status
Date: Wed, 24 Jul 2024 05:57:02 -0700	[thread overview]
Message-ID: <000000000000883205061dfdd0b3@google.com> (raw)
In-Reply-To: <000000000000ce2dde0610db47a8@google.com>

syzbot suspects this issue was fixed by commit:

commit eba63df7eb1f95df6bfb67722a35372b6994928d
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date:   Fri May 10 07:11:46 2024 +0000

    Revert "media: v4l2-ctrls: show all owned controls in log_status"

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=146553b5980000
start commit:   c942a0cd3603 Merge tag 'for_linus' of git://git.kernel.org..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=98d5a8e00ed1044a
dashboard link: https://syzkaller.appspot.com/bug?extid=9948f8e188482c5d1a3e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=100b025f180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11abdfc8980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Revert "media: v4l2-ctrls: show all owned controls in log_status"

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-07-24 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08  9:17 [syzbot] [media?] possible deadlock in v4l2_ctrl_handler_log_status syzbot
2024-02-09  8:11 ` Hillf Danton
2024-02-09  8:34   ` syzbot
2024-02-09 13:58 ` syzbot
2024-07-24 12:57 ` syzbot [this message]

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=000000000000883205061dfdd0b3@google.com \
    --to=syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=daniel.almeida@collabora.com \
    --cc=hdanton@sina.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=umang.jain@ideasonboard.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.