From: Mimi Zohar <zohar@linux.ibm.com>
To: Sumit Garg <sumit.garg@linaro.org>,
torvalds@linux-foundation.org, jarkko@kernel.org,
peterz@infradead.org
Cc: 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] KEYS: trusted: Remove redundant static calls usage
Date: Thu, 05 Oct 2023 12:45:06 -0400 [thread overview]
Message-ID: <e1570b53b991301ee73be185244ef43487bf5961.camel@linux.ibm.com> (raw)
In-Reply-To: <20231005133306.379718-1-sumit.garg@linaro.org>
Hi Summit,
On Thu, 2023-10-05 at 19:03 +0530, Sumit Garg 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.
Split the above paragraph into two sentences.
> However, the usage of static call invocations for trusted_key_init()
> and trusted_key_exit() doesn't adds any value neither from performance
> point and nor there is any security benefit.
don't add any value from either a performance or security
perspective.
> Hence switch to use indirect
> function calls instead.
>
> Note here that although it will fix the current crash reported. But
> ultimately we need fix up static calls infrastructure to either support
> its future usage from module __init and __exit functions or not.
The first line is a sentence fragment. Please replace the period with
a comma.
report, ultimately the static call call infrastructure should ...
>
> Reported-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
> Closes: https://lore.kernel.org/lkml/ZRhKq6e5nF%2F4ZIV1@fedora/#t
Replace "Closes" with "Link".
> Fixes: 5d0682be3189 ("KEYS: trusted: Add generic trusted keys framework")
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
--
thanks,
Mimi
prev parent reply other threads:[~2023-10-05 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 13:33 Sumit Garg
2023-10-05 16:45 ` Mimi Zohar [this message]
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=e1570b53b991301ee73be185244ef43487bf5961.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=42.hyeyoo@gmail.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=jarkko@kernel.org \
--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 \
/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®