public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: davej@redhat.com, netdev@vger.kernel.org
Subject: Re: ipqueue allocation failure.
Date: Wed, 20 Apr 2011 07:27:47 +0200	[thread overview]
Message-ID: <1303277267.2756.14.camel@edumazet-laptop> (raw)
In-Reply-To: <20110419.204105.68144653.davem@davemloft.net>

Le mardi 19 avril 2011 à 20:41 -0700, David Miller a écrit :
> From: Dave Jones <davej@redhat.com>
> Date: Tue, 19 Apr 2011 21:42:22 -0400
> 
> > Not catastrophic, but ipqueue seems to be too trusting of what it gets
> > passed from userspace, and passes it on down to the page allocator,
> > where it will spew warnings if the page order is too high.
> > 
> > __ipq_rcv_skb has several checks for lengths too small, but doesn't
> > seem to have any for oversized ones.   I'm not sure what the maximum
> > we should check for is. I'll code up a diff if anyone has any ideas
> > on a sane maximum.
> 
> Maybe the thing to do is to simply pass __GFP_NOWARN to nlmsg_new()
> in netlink_ack()?
> 
> Anyone else have a better idea?
> --

It should be fine, since we already checked sk->sk_sndbuf in
netlink_sendmsg()

if (len > sk->sk_sndbuf - 32)
	goto out;

Maybe the 32 magic value is too small to take into account
struct nlmsgerr that is prepended in netlink_ack()

Hmm, no, sizeof(struct nlmsgerr) is 20




  reply	other threads:[~2011-04-20  5:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  1:42 ipqueue allocation failure Dave Jones
2011-04-20  3:41 ` David Miller
2011-04-20  5:27   ` Eric Dumazet [this message]
2011-05-28  0:36   ` [PATCH] Use unsigned variables for packet lengths in ip[6]_queue Dave Jones
2011-06-02 19:24     ` Dave Jones
2011-06-02 20:57     ` David Miller
2011-06-07 12:59       ` Patrick McHardy
2011-06-07 14:19         ` Patrick McHardy
2011-06-07 14:39           ` Dave Jones
2011-06-07 15:19             ` Patrick McHardy
2011-06-03 10:07     ` Pablo Neira Ayuso
2011-04-21 15:13 ` ipqueue allocation failure Patrick McHardy

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=1303277267.2756.14.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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