From: Borislav Petkov <bp@alien8.de>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: linux-crypto@vger.kernel.org, thomas.lendacky@amd.com,
Gary Hook <Gary.Hook@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH crypto-2.6] crypto: ccp: add timeout support in the SEV command
Date: Tue, 11 Sep 2018 15:53:25 +0200 [thread overview]
Message-ID: <20180911135325.GI12094@zn.tnic> (raw)
In-Reply-To: <e327fa7f-2d4d-2181-c3f4-607faf16c9b5@amd.com>
On Mon, Sep 10, 2018 at 02:06:57PM -0500, Brijesh Singh wrote:
> Nothing prevent user from supplying a bogus number. The main question
> is, clamp with what number ?
So you definitely want to forbid too large timeouts - that wouldn't make
any sense anyway. And too small either, because a too small timeout
would make a potentially functioning fw broken.
> IMO, if user is overriding the default timeout number then its possible
> that user is dealing with a buggy firmware which does not work with
> default timeout and silently clamping the value will not help them.
No one said "silently" - you simply say:
"Correcting PSP "Correcting PSP probe timeout to X seconds."
when loading the driver so that the user is aware that the value she
entered might not be an optimal one.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2018-09-11 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1534367485-4386-1-git-send-email-brijesh.singh@amd.com>
2018-08-15 21:11 ` Brijesh Singh
2018-09-04 5:19 ` Herbert Xu
2018-09-12 0:11 ` Brijesh Singh
2018-09-13 5:02 ` Herbert Xu
2018-09-04 8:11 ` Borislav Petkov
2018-09-10 19:06 ` Brijesh Singh
2018-09-11 13:53 ` Borislav Petkov [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=20180911135325.GI12094@zn.tnic \
--to=bp@alien8.de \
--cc=Gary.Hook@amd.com \
--cc=brijesh.singh@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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
Powered by JetHome