From: "Denis V. Lunev" <den@sw.ru>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, jeff@garzik.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, den@openvz.org
Subject: Re: [NET] IPv6 oops bisected
Date: Mon, 08 Oct 2007 10:34:23 +0400 [thread overview]
Message-ID: <4709CF6F.60102@sw.ru> (raw)
In-Reply-To: <20071007.232302.78733656.davem@davemloft.net>
David Miller wrote:
> From: Herbert Xu <herbert@gondor.apana.org.au>
> Date: Mon, 8 Oct 2007 14:19:42 +0800
>
>> On Sun, Oct 07, 2007 at 11:16:08PM -0700, David Miller wrote:
>>> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
>>> index a7db84c..7109ad6 100644
>>> --- a/net/ipv6/route.c
>>> +++ b/net/ipv6/route.c
>>> @@ -1188,7 +1188,7 @@ int ip6_route_add(struct fib6_config *cfg)
>>> if ((cfg->fc_flags & RTF_REJECT) ||
>>> (dev && (dev->flags&IFF_LOOPBACK) && !(addr_type&IPV6_ADDR_LOOPBACK))) {
>>> /* hold loopback dev/idev if we haven't done so. */
>>> - if (dev != dev->nd_net->loopback_dev) {
>>> + if (!dev || (dev != dev->nd_net->loopback_dev)) {
>>> if (dev) {
>>> dev_put(dev);
>>> in6_dev_put(idev);
>> Unfortunately this'll still oops a few lines down when it tries
>> to assign dev->nd_net->loopabck_dev to dev. The issue here is
>> which namespace are we in if dev is NULL.
>
> Good catch.
>
> I'm just going to revert my bogus fix and the original change
> for now. Denis can resubmit the original patch once this
> is resolved.
OK. I am installing Fedora 7 right now...
next prev parent reply other threads:[~2007-10-08 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 12:52 [NET] IPv6 oops bisected Jeff Garzik
2007-10-07 13:33 ` Jeff Garzik
2007-10-07 13:49 ` Denis V. Lunev
2007-10-07 14:56 ` Jeff Garzik
2007-10-08 6:16 ` David Miller
2007-10-08 6:19 ` Herbert Xu
2007-10-08 6:23 ` David Miller
2007-10-08 6:34 ` Denis V. Lunev [this message]
2007-10-08 6:46 ` David Miller
2007-10-08 7:00 ` Denis V. Lunev
2007-10-08 16:02 ` Eric W. Biederman
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=4709CF6F.60102@sw.ru \
--to=den@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=herbert@gondor.apana.org.au \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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