linux-kernel - RE: [3/5] 2.6.21-rc4: known regressions (v2)

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]

Message-ID: <617E1C2C70743745A92448908E030B2A0148323B@scsmsx411.amr.corp.intel.com>
Date:	Mon, 26 Mar 2007 13:01:05 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Thomas Meyer" <thomas@...3r.de>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	<linux-pci@...ey.karlin.mff.cuni.cz>,
	"Greg Kroah-Hartman" <gregkh@...e.de>,
	<linux-pci@...ey.karlin.mff.cuni.cz>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Len Brown" <lenb@...nel.org>
Subject: RE: [3/5] 2.6.21-rc4: known regressions (v2)

> What I'm proposing we do is move the irq allocation code out of
> pci_enable_device and the irq freeing code out of pci_disable_device
> in the future.

Sounds rational ... in a world that wasn't dominated by PCI it would
seem to be the logical approach (since the irq code would have much
more utility independent of the PCI code).

> Tony, Len before we merge any fixes for 2.6.21-rcX I'd like to at
> least get an ack on the long term direction.

Long-term-direction-acked-by: Tony Luck <tony.luck@...el.com>

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