From: David Miller <davem@davemloft.net>
To: kuznet@ms2.inr.ac.ru
Cc: jarkao2@gmail.com, nhorman@tuxdriver.com, netdev@vger.kernel.org,
mbizon@freebox.fr, dada1@cosmosbay.com, pekkas@netcore.fi,
jmorris@namei.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] fix NULL pointer + success return in route lookup path
Date: Mon, 22 Jun 2009 02:42:43 -0700 (PDT) [thread overview]
Message-ID: <20090622.024243.70686716.davem@davemloft.net> (raw)
In-Reply-To: <20090622085950.GA26598@ms2.inr.ac.ru>
From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Date: Mon, 22 Jun 2009 12:59:50 +0400
> On Mon, Jun 22, 2009 at 05:43:15AM +0000, Jarek Poplawski wrote:
>> Maybe it can work, but it needs a thorough checking now and adds a new
>> code path to track later while looking for bugs. So, I wonder if it's
>> not better to link such dsts in rt_intern_hash anyway, probably as a
>> separate list, scanned only for expired entries.
>
> Such a list already exists, it is gc list in core/dst.c.
>
> The fix to the problem could be replacing rt_drop() with rt_free()
> (adding rt_free() after the patch, which deleted rt_drop()), something like:
>
> if (!rt_caching(dev_net(rt->u.dst.dev))) {
> /* ..... */
> + rt_free(rt);
> goto report_and_exit;
> }
>
> rt_free() will put the route on that gc list and it will be releases
> as soon as refcnt becomes 0.
That should work.
Can someone put together a formal patch and give it at least
a quick test?
Thanks!
next prev parent reply other threads:[~2009-06-22 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 17:18 [PATCH] fix NULL pointer + success return in route lookup path Neil Horman
2009-06-20 8:15 ` David Miller
2009-06-20 12:37 ` Jarek Poplawski
2009-06-20 16:39 ` Jarek Poplawski
2009-06-20 17:11 ` Neil Horman
2009-06-20 17:23 ` Jarek Poplawski
2009-06-20 23:47 ` David Miller
2009-06-21 17:11 ` Neil Horman
2009-06-22 5:43 ` Jarek Poplawski
2009-06-22 8:59 ` Alexey Kuznetsov
2009-06-22 9:42 ` David Miller [this message]
2009-06-22 10:56 ` Neil Horman
2009-06-22 11:00 ` Jarek Poplawski
2009-06-22 11:08 ` Neil Horman
2009-06-22 12:18 ` Jarek Poplawski
2009-06-22 15:10 ` Neil Horman
2009-06-22 11:29 ` Alexey Kuznetsov
2009-06-22 12:04 ` Jarek Poplawski
2009-06-20 16:44 ` Neil Horman
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=20090622.024243.70686716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dada1@cosmosbay.com \
--cc=jarkao2@gmail.com \
--cc=jmorris@namei.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mbizon@freebox.fr \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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).