From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: sowmini.varadhan@oracle.com, 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: Sat, 18 Jul 2015 11:06:26 -0700 [thread overview]
Message-ID: <1437242786.24289.11.camel@perches.com> (raw)
In-Reply-To: <20150717.181825.641987192390100037.davem@davemloft.net>
On Fri, 2015-07-17 at 18:18 -0700, David Miller wrote:
> From: Joe Perches <joe@perches.com> Date: Fri, 17 Jul 2015 16:07:02 -0700
> > On Fri, 2015-07-17 at 22:00 +0200, Sowmini Varadhan wrote:
> >> __vxlan_find_mac invokes ether_addr_equal on the eth_addr field,
> >> which triggers unaligned access messages, so rearrange vxlan_fdb
> >> to avoid this in the most non-intrusive way.
> > What arch does this?
> Sparc, MIPS, etc.
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.
---
arch/sparc/kernel/unaligned_64.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/sparc/kernel/unaligned_64.c b/arch/sparc/kernel/unaligned_64.c
index 62098a8..6b7aeb7 100644
--- a/arch/sparc/kernel/unaligned_64.c
+++ b/arch/sparc/kernel/unaligned_64.c
@@ -294,13 +294,9 @@ static void kernel_mna_trap_fault(int fixup_tstate_asi)
static void log_unaligned(struct pt_regs *regs)
{
- static DEFINE_RATELIMIT_STATE(ratelimit, 5 * HZ, 5);
+ pr_debug_ratelimited("Kernel unaligned access at TPC[%lx] %pS\n",
+ regs->tpc, (void *)regs->tpc);
- if (__ratelimit(&ratelimit)) {
- printk("Kernel unaligned access at TPC[%lx] %pS\n",
- regs->tpc, (void *) regs->tpc);
- }
-}
asmlinkage void kernel_unaligned_trap(struct pt_regs *regs, unsigned int insn)
{
next prev parent reply other threads:[~2015-07-18 18:06 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 [this message]
2015-07-19 5:23 ` David Miller
2015-07-19 12:01 ` Sowmini Varadhan
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=1437242786.24289.11.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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).