Netdev List
 help / color / mirror / Atom feed
From: Alexander Aring <aring@mojatatu.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org,
	david.palma@ntnu.no, rabinarayans0828@gmail.com,
	jhs@mojatatu.com, stefan@osg.samsung.com,
	linux-wpan@vger.kernel.org, kernel@mojatatu.com
Subject: Re: [PATCH net] net: ipv6: ip6_output: alloc skb with tailroom
Date: Wed, 6 Jun 2018 14:09:20 -0400	[thread overview]
Message-ID: <20180606180853.zimcpxbo3ejxum6g@x220t> (raw)
In-Reply-To: <20180606.135339.2253125602143741999.davem@davemloft.net>

Hi,

On Wed, Jun 06, 2018 at 01:53:39PM -0400, David Miller wrote:
> From: Alexander Aring <aring@mojatatu.com>
> Date: Tue,  5 Jun 2018 18:04:04 -0400
> 
> > This patch adds care about tailroom length for allocate a skb from ipv6
> > level stack. In case of 6lowpan we had the problem the skb runs into a
> > skb_over_panic() in some special length cases. The root was there was no
> > tailroom allocated for the IEEE 802.15.4 checksum, although we had
> > the necessary tailroom specified inside the netdev structure.
> > 
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195059
> > Reported-by: David Palma <david.palma@ntnu.no>
> > Reported-by: Rabi Narayan Sahoo <rabinarayans0828@gmail.com>
> > Signed-off-by: Alexander Aring <aring@mojatatu.com>
> 
> needed_tailroom is an optimization to avoid SKB reallocations
> and adjustments, it is not a guarantee.
> 

okay, then you want to have this patch for net-next? As an optimization?

Of course, when it's open again.

> If you are seeing crashes, it means code is assuming something which
> is not to be assumed.
> 
> Whatever code is involved, it needs to check that the necessary
> tailroom is there and reallocate if necessary, rather than
> blindly pushing past the end of the SKB data.
> 

I see, I will add checks and reallocs (if necessary) in the underlaying
subsystem level.

Thanks for clarifying this.

- Alex

  reply	other threads:[~2018-06-06 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 22:04 [PATCH net] net: ipv6: ip6_output: alloc skb with tailroom Alexander Aring
2018-06-06 17:53 ` David Miller
2018-06-06 18:09   ` Alexander Aring [this message]
2018-06-06 18:11     ` David Miller
2018-06-06 20:26       ` Willem de Bruijn
2018-06-07 16:22         ` Alexander Aring
2018-06-07 16:28           ` Willem de Bruijn

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=20180606180853.zimcpxbo3ejxum6g@x220t \
    --to=aring@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=david.palma@ntnu.no \
    --cc=jhs@mojatatu.com \
    --cc=kernel@mojatatu.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rabinarayans0828@gmail.com \
    --cc=stefan@osg.samsung.com \
    --cc=yoshfuji@linux-ipv6.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