From: David Miller <davem@davemloft.net>
To: ard.biesheuvel@linaro.org
Cc: ebiggers@kernel.org, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
edumazet@google.com, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, jbaron@akamai.com, cpaasch@apple.com,
David.Laight@aculab.com, ycheng@google.com
Subject: Re: [PATCH 2/2] net: fastopen: use endianness agnostic representation of the cookie
Date: Tue, 18 Jun 2019 18:40:26 -0400 (EDT) [thread overview]
Message-ID: <20190618.184026.1967040334284472836.davem@davemloft.net> (raw)
In-Reply-To: <CAKv+Gu-xBCe09B1=GvXBH3V-p7=fOZcdL5pvFi5v19LT0J4KHA@mail.gmail.com>
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date: Tue, 18 Jun 2019 20:40:18 +0200
> Can we first agree on whether we care about this or not? If so, i
> can spin a v2.
Well, how can it possibly work otherwise in deployment scenerios involving
both big and little endian hosts?
next prev parent reply other threads:[~2019-06-18 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 9:32 [PATCH 0/2] net: fastopen: follow-up tweaks for SipHash switch Ard Biesheuvel
2019-06-18 9:32 ` [PATCH 1/2] net: fastopen: make key handling more robust against future changes Ard Biesheuvel
2019-06-18 9:39 ` Eric Dumazet
2019-06-18 9:41 ` Ard Biesheuvel
2019-06-18 9:53 ` Eric Dumazet
2019-06-18 10:02 ` Ard Biesheuvel
2019-06-18 18:18 ` Eric Biggers
2019-06-18 18:19 ` Eric Dumazet
2019-06-18 9:32 ` [PATCH 2/2] net: fastopen: use endianness agnostic representation of the cookie Ard Biesheuvel
2019-06-18 18:22 ` Eric Biggers
2019-06-18 18:40 ` Ard Biesheuvel
2019-06-18 22:40 ` David Miller [this message]
2019-06-18 9:37 ` [PATCH 0/2] net: fastopen: follow-up tweaks for SipHash switch Eric Dumazet
2019-06-18 9:38 ` Ard Biesheuvel
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=20190618.184026.1967040334284472836.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@aculab.com \
--cc=ard.biesheuvel@linaro.org \
--cc=cpaasch@apple.com \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=jbaron@akamai.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.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).