From: Eric Dumazet <eric.dumazet@gmail.com>
To: Artem Savkov <artem.savkov@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG]: missing shinfo with netlink_alloc_large_skb
Date: Thu, 27 Jun 2013 04:50:18 -0700 [thread overview]
Message-ID: <1372333818.3301.226.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130627114432.GA22103@cpv436-motbuntu>
On Thu, 2013-06-27 at 15:44 +0400, Artem Savkov wrote:
> Hello,
>
> I ran into a bug while running trinity with write/writev syscalls. Seems like
> it has been introduced by "netlink: allow large data transfers from user-space"
> commit. nf_fib_input calls skb_clone which expects skb_shinfo to be allocated,
> but netlink_alloc_large_skb doesn't do that, should it?.
> Relevant dmesg log below.
>
Yes, this was discussed and Pablo is working on it
http://marc.info/?l=linux-netdev&m=137232186620827&w=2
prev parent reply other threads:[~2013-06-27 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 11:44 [BUG]: missing shinfo with netlink_alloc_large_skb Artem Savkov
2013-06-27 11:50 ` 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=1372333818.3301.226.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=artem.savkov@gmail.com \
--cc=davem@davemloft.net \
--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