From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: atomlin@redhat.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pshelar@nicira.com, mst@redhat.com, alexander.h.duyck@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [Patch v1] skbuff: Hide GFP_ATOMIC page allocation failures for dropped packets
Date: Mon, 27 May 2013 21:53:08 +0400 [thread overview]
Message-ID: <51A39D84.4090505@cogentembedded.com> (raw)
In-Reply-To: <51A23825.7000303@cogentembedded.com>
Hello.
On 26-05-2013 20:28, Sergei Shtylyov wrote:
>> From: Aaron Tomlin <atomlin@redhat.com>
>> Failed GFP_ATOMIC allocations by the network stack result in dropped
>> packets, which will be received on a subsequent retransmit, and an
>> unnecessary, noisy warning with a kernel backtrace.
>> These warnings are harmless, but they still cause users to panic and
>> file bug reports over dropped packets. It would be better to hide the
>> failed allocation warnings and backtraces, and let retransmits handle
>> dropped packets quietly.
>> Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
>> ---
>> net/core/skbuff.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
>> index af9185d..02139d6 100644
>> --- a/net/core/skbuff.c
>> +++ b/net/core/skbuff.c
>> @@ -236,7 +236,7 @@ struct sk_buff *__alloc_skb(unsigned int size,
>> gfp_t gfp_mask,
>> ? skbuff_fclone_cache : skbuff_head_cache;
>>
>> if (sk_memalloc_socks() && (flags & SKB_ALLOC_RX))
>> - gfp_mask |= __GFP_MEMALLOC;
>> + gfp_mask |= (__GFP_MEMALLOC|__GFP_NOWARN);
> Parens not needed here.
And add spaces around | please, to be consistent with other code.
WBR, Sergei
prev parent reply other threads:[~2013-05-27 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 13:17 [Patch v1] skbuff: Hide GFP_ATOMIC page allocation failures for dropped packets atomlin
2013-05-26 16:28 ` Sergei Shtylyov
2013-05-26 22:00 ` Joe Perches
2013-05-27 17:53 ` Sergei Shtylyov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A39D84.4090505@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=alexander.h.duyck@intel.com \
--cc=atomlin@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).