linux-kernel - [PATCH 0/8] drivers edac sysfs fixes

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

Message-ID: <4697ad51.C2wq7Bw6ISiOLe6E%dougthompson@xmission.com>
Date:	Fri, 13 Jul 2007 10:50:25 -0600
From:	dougthompson@...ssion.com
To:	dougthompson@...ssion.com, greg@...ah.com,
	alan@...rguk.ukuu.org.uki, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: [PATCH 0/8] drivers edac sysfs fixes

This EDAC patch set was applied against: 2.6.22-rc6-mm1

This series of EDAC patches fixes sysfs completion operation as found during
a review of the last -mm submission, and a new low level chipset driver

1) These fixes dealt with EDAC sysfs operation, namely the exiting/releasing of
sysfs objects by the edac core driver, for edac_mc and edac_device classes.

This removes "completion call" operations on sysfs teardown.

The sysfs code now bumps the ref count on the main kobject of each control 
structure to count internal kobjects. The main kobject bumps the 
edac_core module once at its creation waiting until its ref count
goes to zero.  At that point, the control struct is kfree() and
the EDAC CORE module ref count is decrement, thus allowing the 
module to be unloaded.

2) Another fix required some additional simple mods on the edac alloc() and
finalization APIs mods which led to altering all the in tree drivers to
comform. This was necessary to allow the sysfs solution to work correctly

3) A new PASEMI driver is also included in this patch set

-
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/