From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
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: Mon, 12 Dec 2011 10:45:10 +0100 [thread overview]
Message-ID: <4EE5CD26.40806@profihost.ag> (raw)
In-Reply-To: <4ED86B79.4060506@profihost.ag>
Hi,
> Am 01.12.2011 22:05, schrieb Eric Dumazet:
>> Le jeudi 01 décembre 2011 à 15:37 -0500, Josh Boyer a écrit :
>>
>>> Did you mean f2c31e32bf2c31e32b378a665 ?
>>
>> Oh well, yes ;)
>>
>>>> But this patch needs some followup patches (some of them in David net
>>>> tree, not yet in Linus tree)
>>>
>>> 9de79c127cccecb11ae6a21ab1499e87aa222880 (net: fix potential neighbour
>>> race in dst_ifdown()) is in Linus' tree. Which others are missing?
>>
>> Hmm
>>
>> Linus tree :
>>
>> commit 580da35a31f91a594f3090b7a2c39b85cb051a12
>> IB: Fix RCU lockdep splats
>>
>> David tree :
>>
>> commit 218fa90f072e4aeff9003d57e390857f4f35513e
>> ipv4: fix lockdep splat in rt_cache_seq_show
>>
>> commit f7e57044eeb1841847c24aa06766c8290c202583
>> sch_teql: fix lockdep splat
main problem seems to me that all these patches make intensive use of
the "new" helper functions from 69cce1d1404968f78b177a0314f5822d5afdbbfb
So must 69cce1d1404968f78b177a0314f5822d5afdbbfb be backported too?
Stefan
next prev parent reply other threads:[~2011-12-12 9:45 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
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 [this message]
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=4EE5CD26.40806@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=hch@infradead.org \
--cc=jwboyer@gmail.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).