From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] ipv4: fix wildcard search with inet_confirm_addr()
Date: Thu, 14 Nov 2013 11:32:53 +0100 [thread overview]
Message-ID: <5284A6D5.7000804@6wind.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1311132244001.1712@ssi.bg>
Le 13/11/2013 22:27, Julian Anastasov a écrit :
>
> Hello,
>
> On Wed, 13 Nov 2013, Nicolas Dichtel wrote:
>
>> Help of this function says: "in_dev: only on this interface, 0=any interface",
>> but since commit 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>
>
> This patch looks ok to me, thanks!
>
> Reviewed-by: Julian Anastasov <ja@ssi.bg>
>
> Still, I think this is a net-next material
> and you have to wait some days... The net tree that
Ok.
> you are using is missing the changes that remove
> 'extern', so I think you have to port it to net-next
> tree to avoid the conflict in include/linux/inetdevice.h.
Yes, checkpatch already warns about this extern kerword.
Thank you,
Nicolas
next prev parent reply other threads:[~2013-11-14 10:32 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 [this message]
2013-12-10 14:02 ` [PATCH net-next v3] " Nicolas Dichtel
2013-12-11 19:49 ` David Miller
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=5284A6D5.7000804@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=ja@ssi.bg \
--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).