All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: Michal Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Stotland, Inga" <inga.stotland@intel.com>,
	"marcel@holtmann.org" <marcel@holtmann.org>,
	"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
	"denkenz@gmail.com" <denkenz@gmail.com>,
	"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>
Subject: RE: [PATCH BlueZ 0/1] mesh: Convert all crypto to ELL
Date: Thu, 30 May 2019 16:06:15 +0000	[thread overview]
Message-ID: <DEBB0CAA2616974FAE35E4B560B9A4376CB64772@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <20190530065833.acnzga3knthhh3nk@scytale>

Hi Michał,

> 
> Hi,
> 
> On 05/29, Brian Gix wrote:
> > This will have one major side effect in that it will no longer support
> > kernels older than v4.9 (I am personally using v5.0.17).  I am told
> > that (some?) Freescale platforms also will have problems regardless of
> > kernel version.
> 
> Alright, so I agree that it would be up to the vendor (i.e. me ;) to provide a
> patch for older kernels.
> 
> I think the most sensible option would be to patch ELL to use userspace fallback,
> instead of patching bluez. So if you could just make sure that an appropriate
> unit test exists within ELL, I have no objections.

The unit test for AEAD in .../ell/unit/test-cipher.c already makes this report on encryption failures:

if (!success) {
	printf("* Some kernel versions before v4.9 have a known AEAD\n"
		"* bug. If the system running this test is using a\n"
		"* v4.8 or earlier kernel, a failure here is likely\n"
		"* due to that kernel bug.\n");
}

So I will likely be applying the patch as written by this weekend to convert all of mesh crypto to ELL.

Any patching (to ELL or BlueZ) will again become the responsibility of the vendor offering support to these older platforms.  To emphasize this, I will probably also add a note to .../bluez/mesh/README to emphasize both the problem with these older platforms, usage of the ELL unit test to identify, and the required work-around.

Best Regards,
Brian

  reply	other threads:[~2019-05-30 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 17:28 [PATCH BlueZ 0/1] mesh: Convert all crypto to ELL Brian Gix
2019-05-29 17:28 ` [PATCH BlueZ 1/1] mesh: Convert crypto to use ELL wrappers Brian Gix
2019-05-30  6:58 ` [PATCH BlueZ 0/1] mesh: Convert all crypto to ELL Michał Lowas-Rzechonek
2019-05-30 16:06   ` Gix, Brian [this message]
2019-05-31 23:54 ` Gix, Brian

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=DEBB0CAA2616974FAE35E4B560B9A4376CB64772@ORSMSX103.amr.corp.intel.com \
    --to=brian.gix@intel.com \
    --cc=denkenz@gmail.com \
    --cc=inga.stotland@intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=michal.lowas-rzechonek@silvair.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.