From: David Miller <davem@davemloft.net>
To: viro@ZenIV.linux.org.uk
Cc: borisp@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] mellanox: fix the dport endianness in call of __inet6_lookup_established()
Date: Mon, 06 Aug 2018 10:32:58 -0700 (PDT) [thread overview]
Message-ID: <20180806.103258.2021871359763559506.davem@davemloft.net> (raw)
In-Reply-To: <20180804204127.GC15082@ZenIV.linux.org.uk>
From: Al Viro <viro@ZenIV.linux.org.uk>
Date: Sat, 4 Aug 2018 21:41:27 +0100
> __inet6_lookup_established() expect th->dport passed in host-endian,
> not net-endian. The reason is microoptimization in __inet6_lookup(),
> but if you use the lower-level helpers, you have to play by their
> rules...
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Applied to net-next, thanks Al.
prev parent reply other threads:[~2018-08-06 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 20:41 [PATCH] mellanox: fix the dport endianness in call of __inet6_lookup_established() Al Viro
2018-08-06 0:27 ` David Miller
2018-08-06 9:23 ` Boris Pismenny
2018-08-06 17:32 ` 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=20180806.103258.2021871359763559506.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=borisp@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).