netdev - Re: INFO: task can't die in p9_fd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200827162023.GD31016@nautica>
Date:   Thu, 27 Aug 2020 18:20:23 +0200
From:   Dominique Martinet <asmadeus@...ewreck.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     syzbot <syzbot+fbe34b643e462f65e542@...kaller.appspotmail.com>,
        alsa-devel@...a-project.org, daniel.baluta@....com,
        davem@...emloft.net, ericvh@...il.com, kuba@...nel.org,
        lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        lucho@...kov.net, netdev@...r.kernel.org, perex@...ex.cz,
        rminnich@...dia.gov, syzkaller-bugs@...glegroups.com,
        tiwai@...e.com, v9fs-developer@...ts.sourceforge.net
Subject: Re: INFO: task can't die in p9_fd_close

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@....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