netdev - Re: [PATCH] bnx2x: avoid atomic allocations during initialization

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: <20130907.214824.1685385647443815510.davem@davemloft.net>
Date:	Sat, 07 Sep 2013 21:48:24 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	dkravkov@...il.com
Cc:	dmitry@...adcom.com, mschmidt@...hat.com, netdev@...r.kernel.org,
	ariele@...adcom.com, eilong@...adcom.com
Subject: Re: [PATCH] bnx2x: avoid atomic allocations during initialization

From: Dmitry Kravkov <dkravkov@...il.com>
Date: Sat, 7 Sep 2013 12:07:50 +0300

> On Sat, Sep 7, 2013 at 7:29 AM, David Miller <davem@...emloft.net> wrote:
>> Probe should never fail because of an atomic memory allocation if at
>> all possible.
> We here are in open() flow, not probe()

It's the same from my perspective.

Better to drop some packets than have _COMPLETELY INOPERATIVE INTERFACE_.
--
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