All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Luis Henriques" <luis.henriques@linux.dev>,
	"David Howells" <dhowells@redhat.com>
Cc: "Eric Biggers" <ebiggers@kernel.org>, <keyrings@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] keys: update key quotas in key_put()
Date: Mon, 18 Mar 2024 23:14:55 +0200	[thread overview]
Message-ID: <CZX6QS05JAHA.M82GVT11TIQC@kernel.org> (raw)
In-Reply-To: <87msr2qpd9.fsf@brahms.olymp>

On Wed Mar 13, 2024 at 2:37 PM EET, Luis Henriques wrote:
> Luis Henriques <lhenriques@suse.de> writes:
>
> > David Howells <dhowells@redhat.com> writes:
> >
> >> Luis Henriques <lhenriques@suse.de> wrote:
> >>
> >>> Delaying key quotas update when key's refcount reaches 0 in key_put() has
> >>> been causing some issues in fscrypt testing, specifically in fstest
> >>> generic/581.  This commit fixes this test flakiness by dealing with the
> >>> quotas immediately, and leaving all the other clean-ups to the key garbage
> >>> collector.
> >>
> >> Okay, I'll accept this.
> >>
> >
> > That's awesome, thanks a lot David.  And, as Eric requested, I'll send out
> > shortly a follow-up fscrypt-specific patch, which will make generic/581
> > fstest finally pass.
>
> Ping.  Looks like this fell through the cracks...?
>
> I took a quick look at some git trees ('jarkko' and 'dhowells') but
> couldn't see this patch anywhere.
>
> Cheers,

My bad! I'll pick this up now.

BR, Jarkko

  reply	other threads:[~2024-03-18 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 10:13 [PATCH v3] keys: update key quotas in key_put() Luis Henriques
2024-01-30 17:27 ` Jarkko Sakkinen
2024-02-05 12:04 ` David Howells
2024-02-05 13:54   ` Luis Henriques
2024-03-13 12:37     ` Luis Henriques
2024-03-18 21:14       ` Jarkko Sakkinen [this message]
2024-03-18 21:37         ` Jarkko Sakkinen
2024-03-18 21:38         ` Luis Henriques

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=CZX6QS05JAHA.M82GVT11TIQC@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.