linux-kernel - Re: [PATCH v1 3/5] amd64_edac: enforce synchronous probe

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

Date:	Thu, 2 Oct 2014 11:18:00 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Luis R. Rodriguez" <mcgrof@...e.com>
Cc:	Tejun Heo <tj@...nel.org>,
	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	gregkh@...uxfoundation.org, dmitry.torokhov@...il.com,
	tiwai@...e.de, arjan@...ux.intel.com, teg@...m.no,
	rmilasan@...e.com, werner@...e.com, oleg@...hat.com, hare@...e.com,
	bpoirier@...e.de, santosh@...lsio.com, pmladek@...e.cz,
	dbueso@...e.com, linux-kernel@...r.kernel.org,
	Doug Thompson <dougthompson@...ssion.com>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	linux-edac@...r.kernel.org
Subject: Re: [PATCH v1 3/5] amd64_edac: enforce synchronous probe

On Thu, Oct 02, 2014 at 12:39:59AM +0200, Luis R. Rodriguez wrote:
> ...
> and my system was still useless and even end up in some fun page faults,
> but again I think this is all related. I reviewed sysfs / kernfs code
> and didn't see issues there with how symlinks are handled so I started
> reviewing the driver itself a bit and saw it had strong use of sysfs
> on itself and also on helpers such as edac_create_sysfs_mci_device().
> I would not be surprised if the issue lies more in there than elsewhere.

Right, but that would point at sysfs being not asyns-ready, right? I
mean, the driver is just a user of sysfs and doesn't do anything out of
the ordinary in that respect. And the sysfs usage comes from the EDAC
core so I think you'll basically end up marking *all* EDAC drivers as
sync because they all call edac_create_sysfs_mci_device() - you just
happened to run an AMD box and see it there.

This might turn fast into a nasty game if other drivers do similar things
so I'd say this needs to get properly debugged to see what is causing it
and fixed there. And my money goes on that

	WARNING: CPU: 2 PID: 127 at fs/kernfs/dir.c:377 kernfs_get+0x31/0x40()

which is there for some reason and apparently shouldn't be happening...

Just an IMHO of course.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/