linux-kernel - [PATCH 0/4] drivers edac fix misc rc1 issues

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]

Date:	Wed, 25 Jul 2007 14:54:01 -0600
From:	dougthompson@...ssion.com
To:	greg@...ah.com, ralf@...ux-mips.org, egor@...emi.com,
	dougthompson@...ssion.com, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: [PATCH 0/4] drivers edac fix misc rc1 issues

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

This EDAC patch set was applied against: 2.6.23-rc1

4 Patches in this set

1) Fixed workq reset undefined problem and found missing workq
   value reset and possible deadlock as we found in edac_device code.
   Each edac_mc control structure is scanned by a workq trigger event
   and that period valu can be modified by a sysfs control.
   This control didn't update the workq value. Now it does

2) Fixed the sysfs of the edac_pci scanning devices. Removed
   Old incorrect code and now reference counters are used on the kobjects
   and reference count on the edac_core.ko module, to keep it in
   memory until all references have cleared

3) Fixed the missing include/asm-mips/edac.h for MIPS which required
   for proper operation on MIPS

4) Fixed a 'depends on' state for the PPC_PASEMI driver.
   Was originally just PPC, but that was incorrect, and would compile
   on all PPC. Now just PPC_PASEMI builds will build this driver.

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/