From: David Howells <dhowells@redhat.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: dhowells@redhat.com, Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"idryomov@gmail.com" <idryomov@gmail.com>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2] ceph: Fix kernel crash in generic/397 test
Date: Wed, 29 Jan 2025 13:42:06 +0000 [thread overview]
Message-ID: <3669175.1738158126@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAO8a2SjrDL5TqW70P3yyqv8X-B5jfQRg-eMTs9Nbntr8=Mwbog@mail.gmail.com>
Alex Markuze <amarkuze@redhat.com> wrote:
> FYI, This the set of fscrypt of tests that keep failing, w/o this patch.
> Many of these revoke keys mid I/O.
> generic/397
> generic/421 #Test revoking an encryption key during concurrent I/O.
> generic/429. #Test revoking an encryption key during concurrent I/O.
> And additional fscrypt races
> generic/440. #Test revoking an encryption key during concurrent I/O.
> generic/580 #Testing the different keyring policies - also revokes
> keys on open files
> generic/593 #Test adding a key to a filesystem's fscrypt keyring via
> an "fscrypt-provisioning" keyring key.
> generic/595 #Test revoking an encryption key during concurrent I/O.
I presume I don't need to add a key and that these do it for themselves?
David
next prev parent reply other threads:[~2025-01-29 13:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 3:50 [PATCH v2] ceph: Fix kernel crash in generic/397 test Viacheslav Dubeyko
2025-01-17 12:06 ` Ilya Dryomov
2025-01-17 19:18 ` Viacheslav Dubeyko
2025-01-17 21:32 ` David Howells
2025-01-17 22:08 ` Viacheslav Dubeyko
2025-01-20 9:33 ` David Howells
2025-01-20 9:47 ` Alex Markuze
2025-01-27 18:40 ` Viacheslav Dubeyko
2025-01-28 16:13 ` David Howells
2025-01-28 16:57 ` David Howells
2025-01-28 20:01 ` David Howells
2025-01-28 20:16 ` Viacheslav Dubeyko
2025-01-28 22:34 ` David Howells
2025-01-28 22:37 ` Viacheslav Dubeyko
2025-01-29 10:39 ` Alex Markuze
2025-01-29 13:42 ` David Howells [this message]
2025-01-29 13:54 ` Alex Markuze
2025-01-29 13:41 ` David Howells
2025-01-29 19:16 ` Viacheslav Dubeyko
2025-02-14 20:29 ` David Howells
2025-02-14 20:54 ` Viacheslav Dubeyko
2025-04-15 17:59 ` Viacheslav Dubeyko
2025-06-01 16:23 ` Ilya Dryomov
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=3669175.1738158126@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.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 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.