From: Eric Dumazet <eric.dumazet@gmail.com>
To: ramesh.nagappa@gmail.com
Cc: bnramesh@yahoo.com, davem@davemloft.net, edumazet@google.com,
ebiederm@xmission.com, xemul@parallels.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ramesh Nagappa <ramesh.nagappa@ericsson.com>
Subject: Re: [PATCH] net: Fix skb_under_panic oops in neigh_resolve_output
Date: Fri, 05 Oct 2012 08:27:25 +0200 [thread overview]
Message-ID: <1349418445.21172.11.camel@edumazet-glaptop> (raw)
In-Reply-To: <1349406325-3157-1-git-send-email-ramesh.nagappa@gmail.com>
On Thu, 2012-10-04 at 20:05 -0700, ramesh.nagappa@gmail.com wrote:
> From: Ramesh Nagappa <ramesh.nagappa@ericsson.com>
>
> The retry loop in neigh_resolve_output() and neigh_connected_output()
> call dev_hard_header() with out reseting the skb to network_header.
> This causes the retry to fail with skb_under_panic. The fix is to
> reset the network_header within the retry loop.
>
> Signed-off-by: Ramesh Nagappa <ramesh.nagappa@ericsson.com>
> Reviewed-by: Shawn Lu <shawn.lu@ericsson.com>
> Reviewed-by: Robert Coulson <robert.coulson@ericsson.com>
> Reviewed-by: Billie Alsup <billie.alsup@ericsson.com>
> ---
> net/core/neighbour.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index 117afaf..f50c542 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -1313,6 +1313,7 @@ int neigh_resolve_output(struct neighbour *neigh, struct sk_buff *skb)
>
> do {
> seq = read_seqbegin(&neigh->ha_lock);
> + __skb_pull(skb, skb_network_offset(skb));
This __skb_pull() could be done before the read_seqbegin() to keep the
protected section short.
> err = dev_hard_header(skb, dev, ntohs(skb->protocol),
> neigh->ha, NULL, skb->len);
> } while (read_seqretry(&neigh->ha_lock, seq));
> @@ -1342,10 +1343,9 @@ int neigh_connected_output(struct neighbour *neigh, struct sk_buff *skb)
> unsigned int seq;
> int err;
>
> - __skb_pull(skb, skb_network_offset(skb));
> -
> do {
> seq = read_seqbegin(&neigh->ha_lock);
> + __skb_pull(skb, skb_network_offset(skb));
This __skb_pull() could be done before the read_seqbegin() to keep the
protected section short.
> err = dev_hard_header(skb, dev, ntohs(skb->protocol),
> neigh->ha, NULL, skb->len);
> } while (read_seqretry(&neigh->ha_lock, seq));
Thanks
next prev parent reply other threads:[~2012-10-05 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 3:05 [PATCH] net: Fix skb_under_panic oops in neigh_resolve_output ramesh.nagappa
2012-10-05 6:27 ` Eric Dumazet [this message]
2012-10-05 16:33 ` Ramesh Nagappa
2012-10-05 16:59 ` Eric Dumazet
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=1349418445.21172.11.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bnramesh@yahoo.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ramesh.nagappa@ericsson.com \
--cc=ramesh.nagappa@gmail.com \
--cc=xemul@parallels.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