linux-kernel - Re: sun50i-a64-pinctrl WARN

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-next>] [day] [month] [year] [list]

Message-ID: <20170317144422.GD5078@htj.duckdns.org>
Date:   Fri, 17 Mar 2017 10:44:22 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Icenowy Zheng <icenowy@...c.xyz>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Adam Borowski <kilobyte@...band.pl>,
        Andre Przywara <andre.przywara@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349

On Fri, Mar 17, 2017 at 10:28:34PM +0800, Icenowy Zheng wrote:
> > It's warning that the device has resources associated with it on
> > probe. There gotta be something fishy going on with the probing
> > sequence. How reproducible is the problem?
> 
> Do you mean in the first probing trial the driver didn't clean up well?

Possibly but devres should have released all resources after the
previous probe failure or driver disassociation, so I have no idea how
there can be resources left on that list.

> With the same driver I didn't see this problem in 4.11-rc{1,2}.

devres hasn't changed, so I have no idea what changed that.  Which
kernels are affected?  Can you bisect if the problem is easily
reproducible?

Thanks.

-- 
tejun