linux-kernel - Re: Linux v2.6.21-rc3

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: <m1lki0rju6.fsf@ebiederm.dsl.xmission.com>
Date:	Tue, 13 Mar 2007 14:04:33 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Greg KH <gregkh@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: Linux v2.6.21-rc3

Greg KH <gregkh@...e.de> writes:

> I do not think this should be reverted, as the odds that some one will
> rename their network device to be "irq" or something else that is in the
> pci device's directory is pretty slim.  It also only shows up if
> CONFIG_SYSFS_DEPRECATED is disabled, not the common option.

Ah.  I missed that last little bit.

> But I am still working on it, I sent you and Kay a patch that, while it
> locks up at boot time, should be close to what we need to address this
> :)

Hmm.  I haven't seen that one.

>> - pci_save_state, pci_restore_state are broken and have been for a
>>   while if used on anything besides plain pci (pci-x, pci-e and msi)
>>   and are not used in pairs. (gregkh and Andrew have the patches to 
>>   correct this).
>
> I think these are already in Linus's tree right now, right?

Oops I missed that.

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