[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171207.145329.1140922105125090186.davem@davemloft.net>
Date: Thu, 07 Dec 2017 14:53:29 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: antoine.tenart@...e-electrons.com
Cc: gregory.clement@...e-electrons.com,
thomas.petazzoni@...e-electrons.com,
miquel.raynal@...e-electrons.com, nadavh@...vell.com,
mw@...ihalf.com, stefanc@...vell.com, ymarkman@...vell.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 1/6] net: mvpp2: only free the TSO header
buffers when it was allocated
From: Antoine Tenart <antoine.tenart@...e-electrons.com>
Date: Thu, 7 Dec 2017 09:48:58 +0100
> This patch adds a check to only free the TSO header buffer when its
> allocation previously succeeded.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@...e-electrons.com>
No, please keep this as a failure to bring up.
Even if you emit a log message, it is completely unintuitive to
have netdev features change on the user just because of a memory
allocation failure.
Powered by blists - more mailing lists