linux-kernel - Re: [butterfly_attach] WARNING: CPU: 0 PID: 198 at fs/sysfs/dir.c:31 sysfs_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-prev] [day] [month] [year] [list]

Message-ID: <20171108120507.ajg4zcrbeykpn66w@sirena.co.uk>
Date:   Wed, 8 Nov 2017 12:05:07 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-spi@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [butterfly_attach] WARNING: CPU: 0 PID: 198 at fs/sysfs/dir.c:31
 sysfs_warn_dup+0x71/0x97

On Wed, Nov 08, 2017 at 07:51:27PM +0800, Fengguang Wu wrote:

> Another option is to disable the butterfy driver in 0day boot tests.
> We've actually accumulated a kconfig enable/disable list over time.

That'd certainly avoid the reports, though it will mean if anyone else
runs the same testing we'll have to go through the same thing with them.
It is more tractable than anything else seems to be though.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)