[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CYLHS5HX5TXF.1CD2QEVLGTHI0@suppilovahvero>
Date: Mon, 22 Jan 2024 21:45:57 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Luis Henriques" <lhenriques@...e.de>
Cc: "David Howells" <dhowells@...hat.com>, "Eric Biggers"
<ebiggers@...nel.org>, <keyrings@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2] keys: update key quotas in key_put()
On Mon Jan 22, 2024 at 1:50 PM EET, Luis Henriques wrote:
> "Jarkko Sakkinen" <jarkko@...nel.org> writes:
>
> > On Mon Jan 15, 2024 at 12:03 PM UTC, Luis Henriques wrote:
> >> Delaying key quotas update when key's refcount reaches 0 in key_put() has
> >> been causing some issues in fscrypt testing. This patches fixes this test
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > This commit fixes the test
> >
> >> flakiness by dealing with the quotas immediately, but leaving all the other
> >> clean-ups to the key garbage collector. Unfortunately, this means that we
> >> also need to switch to the irq-version of the spinlock that protects quota.
> >
> > The commit message fails to describe the implementation changes.
> >
> > You have a motivation paragraph but you also need to add implementation
> > paragraph, which describes how the code changes reflect the motivation.
>
> Thank you for your feedback, Jarkko. I'll address your comments in v3.
>
> But before sending another rev, I'll wait a bit more, maybe David also has
> some feedback on the implementation.
>
> Cheers,
Take you time :-)
BR, Jarkko
Powered by blists - more mailing lists