From: "Natalie Protasevich" <protasnb@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: An ioctl to delete an ipv6 tunnel leads to a kernel panic
Date: Tue, 12 Feb 2008 22:00:36 -0800 [thread overview]
Message-ID: <32209efe0802122200w21403331k953be3da80ede52b@mail.gmail.com> (raw)
In-Reply-To: <20080212.214946.168597748.davem@davemloft.net>
On Feb 12, 2008 9:49 PM, David Miller <davem@davemloft.net> wrote:
> From: "Natalie Protasevich" <protasnb@gmail.com>
> Date: Mon, 11 Feb 2008 12:49:12 -0800
>
> > Possible reason for this failure was identified and tested by the
> > submitter and several other reporters that ran into the same problem.
> > Can the patch be reviewed and pushed upstream if accepted (if the
> > problem hasn't been addressed already)?
>
> There are a lot of bogus patches in there, using funny
> long variable names, and mainly they were meant for testing
> and verification of the problem.
>
> I see no real serious patch submissions in that bug and furthermore
> the patch, if ready, should be submitted formally here to netdev not
> rot in bugzilla.
>
> Finally, what appears to be the proposal cannot be correct. If the
> fib6_add_rt2node() finds that the new route is a duplicate, we should
> disconnect it from the fn->leaf and do a dst_release(). The bug
> appears to be rather that we leave the route attached to the fn, not
> that we drop the refrence to it.
>
> Thank you.
Thanks David for looking in this. I will give this thought to the
diligent reporters, unless someone on the net team can produce a patch
for them to test.
Sometimes reporters come up with patches and I always try to make sure
the patches end up on appropriate mailing list, and I will continue
doing so :)
Regards,
--Natalie
>
prev parent reply other threads:[~2008-02-13 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:49 An ioctl to delete an ipv6 tunnel leads to a kernel panic Natalie Protasevich
2008-02-13 5:49 ` David Miller
2008-02-13 6:00 ` Natalie Protasevich [this message]
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=32209efe0802122200w21403331k953be3da80ede52b@mail.gmail.com \
--to=protasnb@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).