From: Jason Wang <jasowang@redhat.com>
To: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Eric Dumazet <edumazet@google.com>, jwboyer@redhat.com
Subject: macvlan crash in 3.9
Date: Tue, 21 May 2013 11:19:28 +0800 [thread overview]
Message-ID: <519AE7C0.5090104@redhat.com> (raw)
Hello David:
We see macvlan crash in 3.9 because the precise packet length estimation
tries to use the transport header which hasn't been set. This has been
fixed in 3.10 and looks like at least the following commits needs to be
backported to 3.9 stable:
set transport header for untrusted packets:
9b4d669bc06c215d64f56f1eb0d4eb96e14d689d
38502af77e07b5d6650b9ff99a0b482d86366592
c1aad275b0293d2b1905ec95a945422262470684
f9ca8f74399f9195fd8e01f67a8424a8d33efa55
15e5a030716468dce4032fa0f398d840fa2756f6
and the commits that introduces skb_transport_header_was_set():
fda55eca5a33f33ffcd4192c6b2d75179714a52c
Thanks
reply other threads:[~2013-05-21 3:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=519AE7C0.5090104@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jwboyer@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).