[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1379382102.4751.2.camel@edumazet-glaptop>
Date: Mon, 16 Sep 2013 18:41:42 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: David Miller <davem@...emloft.net>
Cc: ebiederm@...ssion.com, edumazet@...gle.com, jiri@...nulli.us,
alexander.h.duyck@...el.com, amwang@...hat.com,
netdev@...r.kernel.org, fruggeri@...stanetworks.com
Subject: Re: [PATCH net-next] net loopback: Set loopback_dev to NULL when
freed
On Mon, 2013-09-16 at 21:34 -0400, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@...il.com>
> Date: Mon, 16 Sep 2013 17:50:51 -0700
>
> > On Mon, 2013-09-16 at 16:52 -0700, Eric W. Biederman wrote:
> >> It has recently turned up that we have a number of long standing bugs
> >> in the network stack cleanup code with use of the loopback device
> >> after it has been freed that have not turned up because in most cases
> >> the storage allocated to the loopback device is not reused, when those
> >> accesses happen.
> >>
> >> Set looback_dev to NULL to trigger oopses instead of silent data corrupt
> >> when we hit this class of bug.
> >>
> >> Signed-off-by: "Eric W. Biederman" <ebiederm@...ssion.com>
> >> ---
> >
> > Acked-by: Eric Dumazet <edumazet@...gle.com>
>
> I'd like to apply this to 'net', any objections?
No objections from me.
--
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