netdev - Re: [PATCH net] amd-xgbe: Add the __GFP_NOWARN flag to Rx buffer allocation

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: <5591BD0B.6020802@amd.com>
Date:	Mon, 29 Jun 2015 16:47:55 -0500
From:	Tom Lendacky <thomas.lendacky@....com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>
Subject: Re: [PATCH net] amd-xgbe: Add the __GFP_NOWARN flag to Rx buffer
 allocation

On 06/29/2015 11:27 AM, David Miller wrote:
> From: Tom Lendacky <thomas.lendacky@....com>
> Date: Mon, 29 Jun 2015 11:22:12 -0500
>
>> When allocating Rx related buffers, alloc_pages is called using an order
>> number that is decreased until successful. A system under stress can
>> experience failures during this allocation process resulting in a warning
>> being issued. This message can be of concern to end users even though the
>> failure is not fatal. Since the failure is not fatal and can occur
>> multiple times, the driver should include the __GFP_NOWARN flag to
>> suppress the warning message from being issued.
>>
>> Signed-off-by: Tom Lendacky <thomas.lendacky@....com>
>
> Applied, thanks.
>

Hi David,

Can this be queued up for stable 4.0/4.1 (it isn't applicable before
3.19)?

Thanks,
Tom
--
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