From: Jarek Poplawski <jarkao2@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, mbizon@freebox.fr, dada1@cosmosbay.com,
kuznet@ms2.inr.ac.ru, davem@davemloft.net, pekkas@netcore.fi,
jmorris@namei.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] fix NULL pointer + success return in route lookup path
Date: Sat, 20 Jun 2009 18:39:25 +0200 [thread overview]
Message-ID: <4A3D10BD.3050301@gmail.com> (raw)
In-Reply-To: <4A3CD7EC.2040904@gmail.com>
Jarek Poplawski wrote, On 06/20/2009 02:37 PM:
> Neil Horman wrote, On 06/19/2009 07:18 PM:
>
>> Don't drop route if we're not caching
...
>> route.c | 14 ++++++++++++--
>> 1 file changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
>> index cd76b3c..65b3a8b 100644
>> --- a/net/ipv4/route.c
>> +++ b/net/ipv4/route.c
>> @@ -1085,8 +1085,16 @@ restart:
>> now = jiffies;
>>
>> if (!rt_caching(dev_net(rt->u.dst.dev))) {
>> - rt_drop(rt);
One more question: if this rt is assigned to an skb, there is only
skb_dst_drop() in kfree_skb(), but it seems we skip rt_free() part,
or I miss something?
Jarek P.
>> - return 0;
>> + /*
>> + * If we're not caching, just tell the caller we
>> + * were successful and don't touch the route. The
>> + * caller hold the sole reference to the cache entry, and
>> + * it will be released when the caller is done with it.
>> + * If we drop it here, the callers have no way to resolve routes
>> + * when we're not caching. Instead, just point *rp at rt, so
>> + * the caller gets a single use out of the route
>> + */
>> + goto report_and_exit;
>> }
>>
>> rthp = &rt_hash_table[hash].chain;
>> @@ -1217,6 +1225,8 @@ restart:
>> rcu_assign_pointer(rt_hash_table[hash].chain, rt);
>>
>> spin_unlock_bh(rt_hash_lock_addr(hash));
>> +
>> +report_and_exit:
>> if (rp)
>> *rp = rt;
>> else
next prev parent reply other threads:[~2009-06-20 16:39 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 [this message]
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
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=4A3D10BD.3050301@gmail.com \
--to=jarkao2@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--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).