From: Eric Biggers <ebiggers@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: syzbot <syzbot+e3c234427cd464510547@syzkaller.appspotmail.com>,
brendanhiggins@google.com, gregkh@linuxfoundation.org,
heikki.krogerus@linux.intel.com,
laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
rafael.j.wysocki@intel.com, sakari.ailus@linux.intel.com,
syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in media_devnode_release
Date: Thu, 4 Jun 2020 21:20:29 -0700 [thread overview]
Message-ID: <20200605042029.GL2667@sol.localdomain> (raw)
In-Reply-To: <08f732a9-986f-6dcf-87dd-075a9b4605d7@infradead.org>
On Sat, May 23, 2020 at 10:38:50AM -0700, Randy Dunlap wrote:
> On 5/23/20 10:04 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: c11d28ab Add linux-next specific files for 20200522
> > git tree: linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17330172100000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=3f6dbdea4159fb66
> > dashboard link: https://syzkaller.appspot.com/bug?extid=e3c234427cd464510547
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122eacba100000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12fffa9a100000
> >
> > The bug was bisected to:
> >
> > commit 4ef12f7198023c09ad6d25b652bd8748c965c7fa
> > Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > Date: Wed May 13 15:18:40 2020 +0000
> >
> > kobject: Make sure the parent does not get released before its children
>
> Hi,
>
> Greg just sent a revert for this patch:
> https://lore.kernel.org/lkml/20200523152922.GA224858@kroah.com/
>
> so all 3 of these reports should be cleared up soon.
Commit was reverted, so invalidating this bug report:
#syz invalid
prev parent reply other threads:[~2020-06-05 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 17:04 possible deadlock in media_devnode_release syzbot
2020-05-23 17:38 ` Randy Dunlap
2020-06-05 4:20 ` Eric Biggers [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=20200605042029.GL2667@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=brendanhiggins@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=sakari.ailus@linux.intel.com \
--cc=syzbot+e3c234427cd464510547@syzkaller.appspotmail.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.