From: Dave Jones <davej@codemonkey.org.uk>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: ipv6: handle -EFAULT from skb_copy_bits
Date: Tue, 20 Dec 2016 14:34:04 -0500 [thread overview]
Message-ID: <20161220193404.epobyrdaghbrkijd@codemonkey.org.uk> (raw)
In-Reply-To: <20161220.132813.435056880928769245.davem@davemloft.net>
On Tue, Dec 20, 2016 at 01:28:13PM -0500, David Miller wrote:
> This has to do with the SKB buffer layout and geometry, not whether
> the packet is "fragmented" in the protocol sense.
>
> So no, this isn't a criteria for packets being filtered out by this
> point.
>
> Can you try to capture what sk->sk_socket->type and
> inet_sk(sk)->hdrincl are set to at the time of the crash?
>
type:3 hdrincl:0
Dave
next prev parent reply other threads:[~2016-12-20 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 15:47 ipv6: handle -EFAULT from skb_copy_bits Dave Jones
2016-12-17 15:41 ` David Miller
2016-12-17 16:43 ` Dave Jones
2016-12-19 17:03 ` Dave Jones
2016-12-19 19:48 ` David Miller
2016-12-20 0:31 ` Dave Jones
2016-12-20 0:40 ` Dave Jones
2016-12-20 1:36 ` David Miller
2016-12-20 18:17 ` Dave Jones
2016-12-20 18:28 ` David Miller
2016-12-20 19:34 ` Dave Jones [this message]
2016-12-20 19:31 ` Cong Wang
2016-12-20 22:12 ` Dave Jones
2016-12-21 6:09 ` Cong Wang
2016-12-21 12:27 ` Hannes Frederic Sowa
2016-12-21 12:41 ` Hannes Frederic Sowa
2016-12-21 19:04 ` David Miller
2016-12-21 21:33 ` Hannes Frederic Sowa
2016-12-22 1:40 ` Dave Jones
2016-12-22 3:29 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-12-22 16:16 Dave Jones
2016-12-23 17:21 ` David Miller
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=20161220193404.epobyrdaghbrkijd@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.