From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Pravin B Shelar <pshelar@nicira.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vxlan: Wrong type passed to %pIS
Date: Sat, 07 Feb 2015 13:34:27 +0100 [thread overview]
Message-ID: <87wq3tnbn0.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <CAM_iQpWGR6zLrGLGsMPM1Y-z45Nd4XO3X_H1KDTedsz2=5mXng@mail.gmail.com> (Cong Wang's message of "Fri, 6 Feb 2015 21:13:31 -0800")
On Sat, Feb 07 2015, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Fri, Feb 6, 2015 at 6:17 PM, Rasmus Villemoes
> <linux@rasmusvillemoes.dk> wrote:
>> src_ip is a pointer to a union vxlan_addr, one member of which is a
>> struct sockaddr. Passing a pointer to src_ip is wrong; one should pass
>> the value of src_ip itself. Since %pIS formally expects something of
>> type struct sockaddr*, let's pass a pointer to the appropriate union
>> member, though this of course doesn't change the generated code.
>>
>
>
> It is a union, this doesn't harm.
>
Just to be clear: This fixes a real bug. The minimal fix had been
- src_mac, &rdst->remote_ip, &src_ip);
+ src_mac, &rdst->remote_ip, src_ip);
but I through in the cosmetic improvements while the line needed
changing anyway.
> Since you are on it, there is another similar place in vxlan too.
... which is why I didn't change that other occurrence.
Rasmus
next prev parent reply other threads:[~2015-02-07 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 2:17 [PATCH] vxlan: Wrong type passed to %pIS Rasmus Villemoes
2015-02-07 3:35 ` Joe Perches
2015-02-07 12:38 ` Rasmus Villemoes
2015-02-07 5:13 ` Cong Wang
2015-02-07 12:34 ` Rasmus Villemoes [this message]
2015-02-07 23:31 ` Cong Wang
2015-02-09 1:15 ` 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=87wq3tnbn0.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pshelar@nicira.com \
--cc=xiyou.wangcong@gmail.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