From: Eric Dumazet <eric.dumazet@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [netlink] WARNING: at mm/vmalloc.c:1487 __vunmap()
Date: Thu, 27 Jun 2013 01:30:35 -0700 [thread overview]
Message-ID: <1372321835.3301.221.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130627082238.GA6346@localhost>
On Thu, 2013-06-27 at 10:22 +0200, Pablo Neira Ayuso wrote:
> Hi Eric,
>
> Thanks for looking into this.
>
> On Wed, Jun 26, 2013 at 05:42:38AM -0700, Eric Dumazet wrote:
> [...]
> > Nope there are several issues :
> >
> > 1) bug in netlink_alloc_large_skb() because it doesn't account
> > for sizeof(struct skb_shared_info) overhead and initialization.
>
> Indeed, I can send a fix for this.
>
> > 2) Also, skb_clone() on such skb should be forbidden.
> >
> > Example, nl_fib_input() does a nskb = skb_clone(skb)
> >
> > If skb is freed before nskb, then nskb wont know skb->head must be freed
> > by vfree()
> >
> > I don't know...
> >
> > 3) Do we really need this vmalloc stuff, because it sounds like we are
> > going to add yet another test in fast path (in skb_free_head())
>
> We want to send atomic rule-set updates via netlink in one single
> batch message to kernel space. Without vmalloc, I can send up to
> ~20000 rule updates in one single batch.
>
> We considered splitting the updates in smaller batches to make netlink
> happy, but then a process has to own the rule-set base until it has
> finished the update to avoid any interference. However, a broken
> user-space program may (ab)use such ownership to prevents others from
> updating the rule-set.
>
> > 4) Or we must track all skb_clone() netlink calls to attach a destructor
> > to properly to the vfree()
>
> Perhaps we can add a new specific function for this, netlink_skb_clone?
>
You have also to track the kfree_skb() calls done before
you set skb->destructor.
Or set skb->destructor right after netlink_alloc_large_skb()
> I'll be fine to track skb_clone in existing netlink families and
> replace it by such call in case you don't find this solution too
> hackish.
Let see if you can do that, I'll test and review the patches.
I suggest you use build_skb() as in :
static struct sk_buff *netlink_alloc_large_skb(unsigned int size, bool broadcast)
{
struct sk_buff *skb;
void *data;
if (size <= NLMSG_GOODSIZE || broadcast)
return alloc_skb(size, GFP_KERNEL);
size = SKB_DATA_ALIGN(size) +
SKB_DATA_ALIGN(sizeof(struct skb_shared_info));
data = vmalloc(size);
if (!data)
return NULL;
skb = build_skb(data, size);
if (!skb)
vfree(data);
else
skb->head_frag = 0;
return skb;
}
prev parent reply other threads:[~2013-06-27 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 22:01 [netlink] WARNING: at mm/vmalloc.c:1487 __vunmap() Fengguang Wu
2013-06-15 5:57 ` Cong Wang
2013-06-15 6:06 ` Cong Wang
2013-06-17 20:09 ` Pablo Neira Ayuso
2013-06-26 12:42 ` Eric Dumazet
2013-06-27 8:22 ` Pablo Neira Ayuso
2013-06-27 8:30 ` Eric Dumazet [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=1372321835.3301.221.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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