netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Joe Perches <joe@perches.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, alexander.duyck@gmail.com
Subject: Re: [PATCHv2 RFC net-next] net/vxlan: Fix kernel unaligned access in __vxlan_find_mac
Date: Sun, 19 Jul 2015 14:01:34 +0200	[thread overview]
Message-ID: <55AB919E.8030505@oracle.com> (raw)
In-Reply-To: <1437242786.24289.11.camel@perches.com>

On 07/18/2015 08:06 PM, Joe Perches wrote:

> It seems that this code has had unaligned accesses
> on this field even before compare_ether_addr was
> converted to ether_addr_equal.
>
> Is sparc64 the only one that emits / ratelimits that
> unaligned access message?  I looked a little, but I
> didn't find a fixup message when MIPS does unaligned
> accesses.  Are all the other arches silent when
> fixing up unaligned accesses?  Maye adding a generic
> debug only ratelimited message might help remove
> more of these.  As it's not fatal, naybe the sparc64
> message should be KERN_DEBUG/pr_debug.

I'm confused, are we suggesting that we "fix" the unaligned
access by snuffing out the message that complains loudly and correctly
about it?

See also: large block comment above __pksb_trim
about correctly using skb_reserve(). Evidently not being
correctly done for the IPv6-vxlan code path (and possibly
for other encaps too?)

--Sowmini

  parent reply	other threads:[~2015-07-19 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 20:00 [PATCHv2 RFC net-next] net/vxlan: Fix kernel unaligned access in __vxlan_find_mac Sowmini Varadhan
2015-07-17 23:07 ` Joe Perches
2015-07-18  1:18   ` David Miller
2015-07-18 18:06     ` Joe Perches
2015-07-19  5:23       ` David Miller
2015-07-19 12:01       ` Sowmini Varadhan [this message]
2015-07-19 18:38         ` David Miller
2015-07-19 19:07           ` Joe Perches
2015-07-18  4:46   ` Sowmini Varadhan

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=55AB919E.8030505@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --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).