[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a56dfcf00709241503j58cc8f82lbb581f29b17ab3d5@mail.gmail.com>
Date: Mon, 24 Sep 2007 22:03:40 +0000
From: "Dan Merillat" <dan.merillat@...il.com>
To: "Greg KH" <gregkh@...e.de>
Cc: linux-kernel@...r.kernel.org, stable@...nel.org,
"Justin Forbes" <jmforbes@...uxtx.org>,
"Zwane Mwaikambo" <zwane@....linux.org.uk>,
"Theodore Ts'o" <tytso@....edu>,
"Randy Dunlap" <rdunlap@...otime.net>,
"Dave Jones" <davej@...hat.com>,
"Chuck Wolber" <chuckw@...ntumlinux.com>,
"Chris Wedgwood" <reviews@...cw.f00f.org>,
"Michael Krufky" <mkrufky@...uxtv.org>,
"Chuck Ebbert" <cebbert@...hat.com>,
"Domenico Andreoli" <cavokz@...il.com>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
alan@...rguk.ukuu.org.uk, bunk@...sta.de,
"Patrick McHardy" <kaber@...sh.net>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [37/50] Fix inet_diag OOPS.
On 9/24/07, Greg KH <gregkh@...e.de> wrote:
> netlink_run_queue() doesn't handle multiple processes processing the
> queue concurrently. Serialize queue processing in inet_diag to fix
> a oops in netlink_rcv_skb caused by netlink_run_queue passing a
> NULL for the skb.
I just got this one on 2.6.23-RC1, looks the same to me but posting
the oops anyway to doublecheck.
(is it possible to get gmail not to mangle code/patches/oopses without
attaching?)
View attachment "oops.txt" of type "text/plain" (3136 bytes)
Powered by blists - more mailing lists