From: David Miller <davem@davemloft.net>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org, therbert@google.com
Subject: Re: [PATCH] ipv4: fix a potential use after free in fou.c
Date: Fri, 17 Oct 2014 23:46:24 -0400 (EDT) [thread overview]
Message-ID: <20141017.234624.2128135369532839014.davem@davemloft.net> (raw)
In-Reply-To: <1413536027-15700-1-git-send-email-roy.qing.li@gmail.com>
From: roy.qing.li@gmail.com
Date: Fri, 17 Oct 2014 16:53:47 +0800
> From: Li RongQing <roy.qing.li@gmail.com>
>
> pskb_may_pull() maybe change skb->data and make uh pointer oboslete,
> so reload uh and guehdr
>
> Fixes: 37dd0247 ("gue: Receive side for Generic UDP Encapsulation")
> Cc: Tom Herbert <therbert@google.com>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
Applied.
prev parent reply other threads:[~2014-10-18 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 8:53 [PATCH] ipv4: fix a potential use after free in fou.c roy.qing.li
2014-10-18 3:46 ` David Miller [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=20141017.234624.2128135369532839014.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@gmail.com \
--cc=therbert@google.com \
/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).