From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, 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: Thu, 09 Feb 2012 07:44:34 +0100 [thread overview]
Message-ID: <4F336B52.90000@profihost.ag> (raw)
In-Reply-To: <20120208.202651.97221367956126026.davem@davemloft.net>
Am 09.02.2012 02:26, schrieb David Miller:
> From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
> Date: Fri, 03 Feb 2012 09:09:35 +0100
>
>> Hi,
>>
>> attached you find the patch files applying cleanly to 3.0.X.
>>
>>>> I've made my own backport of the patch and removed at least 1-2
>>>> dependencies. Anybody interested?
>>>>
>>>
>>> If you did the work, post it for review.
>>
>> Thanks!
>
> I think you backported way too much, the ->lookup_neigh() dst ops
> abstraction is unnecessary, all of the neighbour hash function
> changes are also completely unnecessary.
>
> All you needed to backport is that bit that abstracts dst->neighbour()
> behind helper routines.
>
> The point of this exercise is not to keep backporting changes until
> the subsequent patch applies cleanly, it's to backport the minimal
> amount necessary to get the effect of the patch you're ultimately
> interested in adding.
>
> I'll work on coming up with something much more sensible tonight.
Thank you very much. As im pinted out i'm not a C dev nor a kernel
hacker. So i was pretty happy that it was working.
Stefan
next prev parent reply other threads:[~2012-02-09 6:44 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 [this message]
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=4F336B52.90000@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=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=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).