All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3b1d4b3d5f7a358bf9a9@syzkaller.appspotmail.com>
To: benjamin.gaignard@collabora.com, hdanton@sina.com,
	 hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
	 laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
	 linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
	 m.szyprowski@samsung.com, mchehab@kernel.org,
	syzkaller-bugs@googlegroups.com,  tfiga@chromium.org
Subject: Re: [syzbot] [media?] [usb?] possible deadlock in vb2_video_unregister_device
Date: Sat, 08 Jun 2024 16:51:02 -0700	[thread overview]
Message-ID: <000000000000b99437061a6996df@google.com> (raw)
In-Reply-To: <0000000000008b96230610c6b3fe@google.com>

syzbot suspects this issue was fixed by commit:

commit 65e6a2773d655172143cc0b927cdc89549842895
Author: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Date:   Sat Mar 2 10:37:08 2024 +0000

    media: usbtv: Remove useless locks in usbtv_video_free()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1009e6f6980000
start commit:   b401b621758e Linux 6.8-rc5
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=eff9f3183d0a20dd
dashboard link: https://syzkaller.appspot.com/bug?extid=3b1d4b3d5f7a358bf9a9
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13ffaae8180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13ef909c180000

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

#syz fix: media: usbtv: Remove useless locks in usbtv_video_free()

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

      parent reply	other threads:[~2024-06-08 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  8:44 [syzbot] [usb?] [media?] possible deadlock in vb2_video_unregister_device syzbot
2024-02-07 11:07 ` Hillf Danton
2024-02-07 11:24   ` syzbot
2024-02-16  5:45 ` Tomasz Figa
2024-02-19 13:10 ` syzbot
2024-02-19 15:49   ` Benjamin Gaignard
2024-02-20  4:49     ` Tomasz Figa
2024-06-08 23:51 ` 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=000000000000b99437061a6996df@google.com \
    --to=syzbot+3b1d4b3d5f7a358bf9a9@syzkaller.appspotmail.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=hdanton@sina.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tfiga@chromium.org \
    /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.