From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@6wind.com
Cc: ja@ssi.bg, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] ipv4: fix wildcard search with inet_confirm_addr()
Date: Wed, 11 Dec 2013 14:49:10 -0500 (EST) [thread overview]
Message-ID: <20131211.144910.1065298780981411778.davem@davemloft.net> (raw)
In-Reply-To: <1386684160-4394-1-git-send-email-nicolas.dichtel@6wind.com>
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Date: Tue, 10 Dec 2013 15:02:40 +0100
> 39a6d0630012 ("[NETNS]: Process inet_confirm_addr in the
> correct namespace."), the code supposes that it will never be NULL. This
> function is never called with in_dev == NULL, but it's exported and may be used
> by an external module.
>
> Because this patch restore the ability to call inet_confirm_addr() with in_dev
> == NULL, I partially revert the above commit, as suggested by Julian.
>
> CC: Julian Anastasov <ja@ssi.bg>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Reviewed-by: Julian Anastasov <ja@ssi.bg>
I personally think that we may be over analyzing this, because if some
external module actually cared, someone would have complained in the
last _5_ years as that's how long the new semantics have been in
place.
Nevertheless, passing in the network namespace explicitly is a bit
nicer than having special behavior for RT_SCOPE_LINE, thus I've
applied this.
Thanks.
prev parent reply other threads:[~2013-12-11 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 14:37 [PATCH net] ipv4: fix wildcard search with inet_confirm_addr() Nicolas Dichtel
2013-11-08 21:24 ` Julian Anastasov
2013-11-13 15:23 ` [PATCH net v2] " Nicolas Dichtel
2013-11-13 21:27 ` Julian Anastasov
2013-11-14 10:32 ` Nicolas Dichtel
2013-12-10 14:02 ` [PATCH net-next v3] " Nicolas Dichtel
2013-12-11 19:49 ` David Miller [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=20131211.144910.1065298780981411778.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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).