All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mikko Rapeli <mikko.rapeli@linaro.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] kmod: enable openssl support by default
Date: Sat, 17 Dec 2022 11:27:50 +0000	[thread overview]
Message-ID: <67a981b00c4913627f6f6f30f79a58ff4b7dcaac.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221125150721.1702791-1-mikko.rapeli@linaro.org>

On Fri, 2022-11-25 at 17:07 +0200, Mikko Rapeli wrote:
> linux-yocto kernel adds openssl-native dependency by default even
> when module signing is still optional. kmod should enable
> openssl support too. This helps see details of signed kernel
> modules and debug issues with module signing. For small systems
> this can still be disabled.

This seems like an easy enough change at first glance, my concern is
dependency chain creep. openssl is slower to build and for example may
depend on perl-native so adding this here can cause builds to slow down
quite a bit more than you'd expect.

I've been holding off merging until I could look at the dependency
chain and see how much difference it actually makes. I've not managed
that yet though.

One option may be to add a "signed-kernel-modules" level distro feature
or perhaps a distro include file, since I suspect this functionality is
going to need other changes to enable and work properly?

Cheers,

Richard


  reply	other threads:[~2022-12-17 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 15:07 [PATCH] kmod: enable openssl support by default Mikko Rapeli
2022-12-17 11:27 ` Richard Purdie [this message]
2022-12-19  6:10   ` [OE-core] " Mikko Rapeli

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=67a981b00c4913627f6f6f30f79a58ff4b7dcaac.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.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 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.