From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stefan Priebe <s.priebe@profihost.ag>,
netdev@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
stable@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000002c
Date: Thu, 01 Dec 2011 21:20:44 +0100 [thread overview]
Message-ID: <1322770844.2750.1.camel@edumazet-laptop> (raw)
In-Reply-To: <20111201182309.GA10686@infradead.org>
Le jeudi 01 décembre 2011 à 13:23 -0500, Christoph Hellwig a écrit :
> On Thu, Dec 01, 2011 at 07:11:51PM +0100, Stefan Priebe wrote:
> > Hi,
> >
> > i'm not quite sure if this is an XFS thing or a tcp thing. As the
> > stacktrace confuses me a little but as it contains
> > xfs_bmap_search_extents and xfs_iunlock. Kernel is 3.0.11 running as
> > 2.6.40.11.
> >
> > [171464.091567] BUG: unable to handle kernel NULL pointer
> > dereference at 000000000000002c
> > [171464.092073] IP: [<ffffffff815494f6>] ipv4_dst_check+0xb6/0x190
> > [171464.092073] PGD 15344e067 PUD 14c821067 PMD 0
> > [171464.092073] Oops: 0002 [#1] SMP
> >
> > Full Stacktrace:
> > http://pastebin.com/raw.php?i=QNg6jD2t
>
> The ? entries mean even the backtrace code things they are unreliable,
> and mos of the cases I've seen they are wrong. In this case it looks
> like the process was doing XFS work before, but the current system call
> indeed is purely in the networking code.
>
> I've changed the cc list to the netdev list which is more appropinquate.
Probably fixed by commit 81d54ec8479a2c695760da
(net: fix NULL dereferences in check_peer_redir())
But this patch needs some followup patches (some of them in David net
tree, not yet in Linus tree)
next prev parent reply other threads:[~2011-12-01 20:20 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ED7C367.3070109@profihost.ag>
2011-12-01 18:23 ` BUG: unable to handle kernel NULL pointer dereference at 000000000000002c Christoph Hellwig
2011-12-01 20:20 ` Eric Dumazet [this message]
2011-12-01 20:37 ` Josh Boyer
2011-12-01 21:05 ` Eric Dumazet
2011-12-02 6:08 ` Stefan Priebe - Profihost AG
2011-12-02 6:17 ` David Miller
2011-12-02 7:19 ` Stefan Priebe - Profihost AG
2011-12-02 17:34 ` David Miller
2011-12-02 18:53 ` Greg KH
2011-12-09 19:01 ` Stefan Priebe
2011-12-09 19:21 ` David Miller
2011-12-10 9:03 ` Stefan Priebe
2012-01-30 8:38 ` Stefan Priebe - Profihost AG
2012-01-30 17:12 ` Greg KH
2012-01-30 17:21 ` David Miller
2012-01-30 18:07 ` David Miller
2012-01-30 18:53 ` Stefan Priebe
2012-01-30 21:48 ` David Miller
2012-01-30 21:56 ` Greg KH
2012-01-31 8:08 ` Stefan Priebe - Profihost AG
2012-02-01 21:21 ` David Miller
2012-02-02 12:55 ` Stefan Priebe - Profihost AG
2012-02-02 15:04 ` Eric Dumazet
2012-02-02 18:37 ` Stefan Priebe
2012-02-02 19:39 ` David Miller
2012-02-03 0:42 ` Greg KH
2012-02-03 6:48 ` Stefan Priebe - Profihost AG
2012-02-03 7:26 ` Eric Dumazet
2012-02-03 8:09 ` Stefan Priebe - Profihost AG
2012-02-03 11:04 ` Eric Dumazet
2012-02-03 15:53 ` Greg KH
2012-02-06 9:04 ` Stefan Priebe - Profihost AG
2012-02-06 9:19 ` Eric Dumazet
2012-02-06 12:47 ` TCP sacked_out and fackets_out inconsistency (Was: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000002c) Ilpo Järvinen
2012-02-08 8:26 ` Stefan Priebe - Profihost AG
2012-02-08 9:15 ` Eric Dumazet
2012-02-08 9:28 ` Eric Dumazet
2012-02-06 9:02 ` BUG: unable to handle kernel NULL pointer dereference at 000000000000002c Stefan Priebe - Profihost AG
2012-02-06 9:16 ` Eric Dumazet
2012-02-06 11:31 ` Stefan Priebe - Profihost AG
2012-02-08 8:24 ` Stefan Priebe - Profihost AG
2012-02-08 16:49 ` Greg KH
2012-02-09 6:43 ` Stefan Priebe - Profihost AG
2012-02-08 20:19 ` David Miller
2012-02-09 1:26 ` David Miller
2012-02-09 6:44 ` Stefan Priebe - Profihost AG
2012-02-09 22:13 ` David Miller
2012-02-10 7:04 ` Stefan Priebe - Profihost AG
2012-02-10 7:07 ` Eric Dumazet
2012-02-10 18:25 ` Eric Dumazet
2012-02-10 20:41 ` David Miller
2012-02-03 15:52 ` Greg KH
2011-12-12 9:45 ` Stefan Priebe - Profihost AG
2011-12-12 12:57 ` Stefan Priebe - Profihost AG
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=1322770844.2750.1.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=stable@vger.kernel.org \
/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