Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be used without shash

From	Daniel Borkmann <daniel@iogearbox.net>
Newsgroups	linux.kernel
Subject	Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be used without shash
Date	2016-12-27 15:20 +0100
Message-ID	<sT0LE-36Q-31@gated-at.bofh.it> (permalink)
References	(3 earlier) <sRYLT-1yK-3@gated-at.bofh.it> <sSyml-1OR-7@gated-at.bofh.it> <sSHIZ-7O7-1@gated-at.bofh.it> <sSI2l-89F-7@gated-at.bofh.it> <sSWI1-nG-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 12/27/2016 10:58 AM, Herbert Xu wrote:
> On Mon, Dec 26, 2016 at 10:08:48AM -0800, Andy Lutomirski wrote:
>>
>> According to Daniel, the networking folks want to let embedded systems
>> include BPF without requiring the crypto core.
>
> Last I checked the IPv4 stack depended on the crypto API so this
> sounds bogus.

I think there's a bit of a mixup here with what I said. To clarify,
requirement back then from tracing folks was that bpf engine and
therefore bpf syscall can be build w/o networking enabled for small
devices, so dependencies preferably need to be kept on a absolute
minimum, same counts for either making it suddenly a depend on
CRYPTO or a select CRYPTO for just those few lines that can be
pulled in from lib/ code instead.

Thread

[RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be used without shash Andy Lutomirski <luto@kernel.org> - 2016-12-24 03:30 +0100
  Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be  used without shash Andy Lutomirski <luto@amacapital.net> - 2016-12-24 03:30 +0100
  Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be  used without shash Andy Lutomirski <luto@amacapital.net> - 2016-12-24 19:00 +0100
    Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can  be used without shash Herbert Xu <herbert@gondor.apana.org.au> - 2016-12-26 09:00 +0100
      Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be  used without shash Ard Biesheuvel <ard.biesheuvel@linaro.org> - 2016-12-26 19:00 +0100
        Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be  used without shash Andy Lutomirski <luto@amacapital.net> - 2016-12-26 19:20 +0100
          Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can  be used without shash Herbert Xu <herbert@gondor.apana.org.au> - 2016-12-27 11:00 +0100
            Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can  be used without shash Daniel Borkmann <daniel@iogearbox.net> - 2016-12-27 15:20 +0100
              Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be  used without shash Andy Lutomirski <luto@amacapital.net> - 2016-12-27 20:10 +0100

csiph-web