linux-kernel - [PATCH 0/6] drivers edac tidying-fix-deadlock-sysfs-docs

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: <469d5886.CpTkivQRuQDgerlV%dougthompson@xmission.com>
Date:	Tue, 17 Jul 2007 18:02:14 -0600
From:	dougthompson@...ssion.com
To:	dougthompson@...ssion.com, greg@...ah.com,
	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: [PATCH 0/6] drivers edac tidying-fix-deadlock-sysfs-docs

From:	Doug Thompson <dougthompson@...ssion.com>

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

6 Patches in this set

1) tidying EXPORT_SYMBOL to EXPORT_SYMBOL_GPL modes, plus blank line removal

2) workq reset deadlock fix. Moved teardown outside of critical section

3) new i82975x driver for ASUS motherboards submitted.

4) EDAC MAINTAINERs updated for new entries, etc

5) found an old internal EDAC structure that was incorrect in the processing
   of block leaf attributes. Amazing it hadn't faulted, just gave bad data.
   Removed that, and replaced with the correct structure from edac_core.h
   Then refactored code to utilize this structure.
   Error occurred in leaf control/attribute presentation to user

6) Enhanced the EDAC documentation to reflect updated status of EDAC
   including the 'edac_device' class of device, which supports
   non-memory type of ECC hardware detectors.

Signed-off-by:  Doug Thompson <dougthompson@...ssion.com>

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