[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1365719193.3887.190.camel@edumazet-glaptop>
Date: Thu, 11 Apr 2013 15:26:33 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Tom Parkin <tparkin@...alix.com>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] udp: don't rereference dst_entry dev pointer on rcv
On Thu, 2013-04-11 at 10:53 -0700, Eric Dumazet wrote:
> On Thu, 2013-04-11 at 09:32 -0700, Eric Dumazet wrote:
>
> > Short update : I do not understand yet why this patch is not working.
> >
> > Normally, the reassembled packet should get the dst from the last skb
> > (the one completing the packet)...
> >
> > I have to make more experiments.
>
> OK I think I've nailed it, please try following patch (I tried it on
> net-next, but it should apply on previous kernels)
By the way I am ashamed by commit 64f3b9e203bd068550
(net: ip_expire() must revalidate route)
Reading its changelog now, I understand I should have fixed this the
way we did today...
:(
Commit 4a94445c9a5c (net: Use ip_route_input_noref() in input path)
added a bug in IP defragmentation handling, in case timeout is fired.
When a frame is defragmented, we use last skb dst field when building
final skb. Its dst is valid, since we are in rcu read section.
But if a timeout occurs, we take first queued fragment to build one ICMP
TIME EXCEEDED message. Problem is all queued skb have weak dst pointers,
since we escaped RCU critical section after their queueing. icmp_send()
might dereference a now freed (and possibly reused) part of memory.
Calling skb_dst_drop() and ip_route_input_noref() to revalidate route is
the only possible choice.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists