From: Dominique Martinet <asmadeus@codewreck.org>
To: Mark Brown <broonie@kernel.org>
Cc: syzbot <syzbot+fbe34b643e462f65e542@syzkaller.appspotmail.com>,
alsa-devel@alsa-project.org, daniel.baluta@nxp.com,
davem@davemloft.net, ericvh@gmail.com, kuba@kernel.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
lucho@ionkov.net, netdev@vger.kernel.org, perex@perex.cz,
rminnich@sandia.gov, syzkaller-bugs@googlegroups.com,
tiwai@suse.com, v9fs-developer@lists.sourceforge.net
Subject: Re: INFO: task can't die in p9_fd_close
Date: Thu, 27 Aug 2020 18:20:23 +0200 [thread overview]
Message-ID: <20200827162023.GD31016@nautica> (raw)
In-Reply-To: <20200826104919.GE4965@sirena.org.uk>
Mark Brown wrote on Wed, Aug 26, 2020:
> On Wed, Aug 26, 2020 at 03:38:15AM -0700, syzbot wrote:
>
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10615b36900000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=a61d44f28687f508
> > dashboard link: https://syzkaller.appspot.com/bug?extid=fbe34b643e462f65e542
> > compiler: gcc (GCC) 10.1.0-syz 20200507
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15920a05900000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a78539900000
> >
> > The issue was bisected to:
> >
> > commit af3acca3e35c01920fe476f730dca7345d0a48df
> > Author: Daniel Baluta <daniel.baluta@nxp.com>
> > Date: Tue Feb 20 12:53:10 2018 +0000
> >
> > ASoC: ak5558: Fix style for SPDX identifier
>
> This bisection is clearly not accurate, I'm guessing the bug is
> intermittent and it was just luck that landed it on this commit.
It's a bug that's been present since day 1 pretty much.
I have a fix that had been overcooking for a while which I had planned
to take in this cycle -- I'll submit to -next during next week, so
hopefully syzbot will be able to spend its time more usefully after
that.
--
Dominique
prev parent reply other threads:[~2020-08-27 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 10:38 INFO: task can't die in p9_fd_close syzbot
2020-08-26 10:49 ` Mark Brown
2020-08-27 16:20 ` Dominique Martinet [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=20200827162023.GD31016@nautica \
--to=asmadeus@codewreck.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rminnich@sandia.gov \
--cc=syzbot+fbe34b643e462f65e542@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).