mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Sumit Garg <sumit.garg@linaro.org>,
	David Howells <dhowells@redhat.com>
Cc: peterz@infradead.org, zohar@linux.ibm.com,
	linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
	jejb@linux.ibm.com, David.Kaplan@amd.com, bp@alien8.de,
	mingo@kernel.org, x86@kernel.org, regressions@leemhuis.info,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: Re: [PATCH v2] KEYS: trusted: Remove redundant static calls usage
Date: Tue, 10 Oct 2023 22:05:50 +0300	[thread overview]
Message-ID: <8a8c14694d5ff62e385163bf0852fd3adb675087.camel@kernel.org> (raw)
In-Reply-To: <CAHk-=whOPoLaWM8S8GgoOPT7a2+nMH5h3TLKtn=R_3w4R1_Uvg@mail.gmail.com>

On Tue, 2023-10-10 at 11:28 -0700, Linus Torvalds wrote:
> On Thu, 5 Oct 2023 at 22:18, Sumit Garg <sumit.garg@linaro.org> wrote:
> > 
> > Static calls invocations aren't well supported from module __init and
> > __exit functions. Especially the static call from cleanup_trusted() led
> > to a crash on x86 kernel with CONFIG_DEBUG_VIRTUAL=y.
> > 
> > However, the usage of static call invocations for trusted_key_init()
> > and trusted_key_exit() don't add any value from either a performance or
> > security perspective. Hence switch to use indirect function calls instead.
> 
> I applied this patch to my tree, since it is a fix for the issue, and
> doesn't change any logic otherwise.
> 
> However, I do note that the code logic is completely broken. It was
> broken before too, and apparently causes no problems, but it's still
> wrong.
> 
> That's a separate issue, and would want a separate patch, but since I
> noticed it when applying this one, I'm replying here:
> 
> > +               trusted_key_exit = trusted_key_sources[i].ops->exit;
> >                 migratable = trusted_key_sources[i].ops->migratable;
> > 
> > -               ret = static_call(trusted_key_init)();
> > +               ret = trusted_key_sources[i].ops->init();
> >                 if (!ret)
> >                         break;
> 
> Note how this sets "trusted_key_exit" even when the ->init() function fails.

Sumit, can you remind me why this continues *on any failure*?

E.g. something like this would make more sense to me:

		ret = trusted_key_sources[i].ops->init();
		if (!ret) {
			static_call_update(trusted_key_seal, trusted_key_sources[i].ops->seal);
			static_call_update(trusted_key_unseal, trusted_key_sources[i].ops->unseal);
			static_call_update(trusted_key_get_random, get_random);
			static_call_update(trusted_key_exit, trusted_key_sources[i].ops->exit);
			migratable = trusted_key_sources[i].ops->migratable;
			break;
		}

		if (ret != -ENODEV)
			break;
`
BR, Jarkko

  reply	other threads:[~2023-10-10 19:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06  5:18 Sumit Garg
2023-10-06  5:56 ` Hyeonggon Yoo
2023-10-10 12:33 ` Jarkko Sakkinen
2023-10-10 13:14   ` Sumit Garg
2023-10-10 13:49     ` Jarkko Sakkinen
2023-10-10 14:19       ` Ahmad Fatoum
2023-10-10 14:31         ` Jarkko Sakkinen
2023-10-10 18:28 ` Linus Torvalds
2023-10-10 19:05   ` Jarkko Sakkinen [this message]
2023-10-10 19:07     ` Jarkko Sakkinen
2023-10-11  5:54     ` Sumit Garg
2023-10-11  5:52   ` Sumit Garg

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=8a8c14694d5ff62e385163bf0852fd3adb675087.camel@kernel.org \
    --to=jarkko@kernel.org \
    --cc=42.hyeyoo@gmail.com \
    --cc=David.Kaplan@amd.com \
    --cc=bp@alien8.de \
    --cc=dhowells@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=regressions@leemhuis.info \
    --cc=sumit.garg@linaro.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®