netdev - Re: Issue with Micrel PCI Network Driver.

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

Date:	Tue, 12 Feb 2013 13:40:40 +0100
From:	Bjørn Mork <bjorn@...k.no>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	<joseph.lutz@...atechweb.com>, <netdev@...r.kernel.org>
Subject: Re: Issue with Micrel PCI Network Driver.

Ben Hutchings <bhutchings@...arflare.com> writes:
> On Tue, 2013-02-12 at 11:10 +0100, Bjørn Mork wrote:
>
>> That should of course be fixed.  But this bug should not prevent
>> userspace from renaming the device, should it? Sounds like a userspace
>> application making too many stupid assumptions to me.  Does it work for
>> network devices attached to other buses?
>
> It prevents userspace from applying a naming policy that incorporates
> the PCI slot number.

Ah, right.  Thanks for explaining.  That makes more sense.


Bjørn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html