[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80272f0259d967fe61dacd1036cbbd9f555b8402.camel@linux.intel.com>
Date: Wed, 08 Jan 2020 18:04:49 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Tadeusz Struk <tadeusz.struk@...el.com>
Cc: keescook@...omium.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, linux-integrity@...r.kernel.org,
labbott@...hat.com
Subject: Re: [PATCH] tpm: handle negative priv->response_len in
tpm_common_read
On Wed, 2020-01-08 at 17:58 +0200, Jarkko Sakkinen wrote:
> On Tue, 2020-01-07 at 14:04 -0800, Tadeusz Struk wrote:
> > The priv->responce_length can hold the size of an response or
> > an negative error code, and the tpm_common_read() needs to handle
> > both cases correctly. Changed the type of responce_length to
> > signed and accounted for negative value in tpm_common_read()
> >
> > Cc: stable@...r.kernel.org
> > Fixes: d23d12484307 ("tpm: fix invalid locking in NONBLOCKING mode")
> > Reported-by: Laura Abbott <labbott@...hat.com>
> > Signed-off-by: Tadeusz Struk <tadeusz.struk@...el.com>
>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
>
> Adding to the next PR.
Applied but had to fix bunch of typos, missing punctaction and
missing parentheses in the commit message. Even checkpatch.pl
was complaining :-/
Thanks.
/Jarkko
Powered by blists - more mailing lists