From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: s.priebe@profihost.ag, gregkh@linuxfoundation.org,
jwboyer@gmail.com, hch@infradead.org, netdev@vger.kernel.org,
david@fromorbit.com, stable@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000002c
Date: Fri, 10 Feb 2012 15:41:41 -0500 (EST) [thread overview]
Message-ID: <20120210.154141.932816326069250336.davem@davemloft.net> (raw)
In-Reply-To: <1328898328.5661.2.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 10 Feb 2012 19:25:28 +0100
> Le vendredi 10 février 2012 à 08:07 +0100, Eric Dumazet a écrit :
>> Le vendredi 10 février 2012 à 08:04 +0100, Stefan Priebe - Profihost AG
>> a écrit :
>> > Hi,
>> >
>> > Am 09.02.2012 23:13, schrieb David Miller:
>> > > From: David Miller <davem@davemloft.net>
>> > > Date: Wed, 08 Feb 2012 20:26:51 -0500 (EST)
>> > >
>> > >> I'll work on coming up with something much more sensible tonight.
>> > >
>> > > Ok, here's what I'm testing right now, please review and test.
>> >
>> > thanks for doing this work! I can't test asap as i can't do udpates just
>> > for fun. I had the "luck" that last time there was the security bug
>> > recarding /proc/mem so i was able to schedule it pretty fast.
>> >
>> > At least the patch applies fine ;-)
>> >
>>
>> I'll do some build/run tests today, please Greg wait a bit before
>> applying this combo patch.
>>
>
> Tests done and no problem met.
Thanks for testing Eric, I'll formally submit this to Greg right now.
next prev parent reply other threads:[~2012-02-10 20:43 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 [this message]
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=20120210.154141.932816326069250336.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jwboyer@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).