From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "slava@dubeyko.com" <slava@dubeyko.com>,
David Howells <dhowells@redhat.com>
Cc: Alex Markuze <amarkuze@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"idryomov@gmail.com" <idryomov@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Patrick Donnelly <pdonnell@redhat.com>
Subject: RE: [RFC PATCH 0/4] ceph: fix generic/421 test failure
Date: Fri, 14 Feb 2025 17:36:17 +0000 [thread overview]
Message-ID: <4e993d6ebadba1ed04261fd5590d439f382ca226.camel@ibm.com> (raw)
In-Reply-To: <4153980.1739553567@warthog.procyon.org.uk>
On Fri, 2025-02-14 at 17:19 +0000, David Howells wrote:
> Okay... I *think* that fixes the hang. There was one case where I saw the
> hang, but I'm not sure that I had your patches applied or whether I'd managed
> to boot the previous kernel that didn't.
>
> So, just with respect to fixing the hang:
>
> Tested-by: David Howells <dhowells@redhat.com>
>
> There's still the issue of encrypted filenames occasionally showing through
> which generic/397 is showing up - but I don't think your patches here fix
> that, right?
>
This patchset doesn't fix the generic/397 issue. I sent another patch ([PATCH
v2] ceph: Fix kernel crash in generic/397 test) [1] before this one with the
fix.
Thanks,
Slava.
[1]
https://lore.kernel.org/all/CAO8a2SjrDL5TqW70P3yyqv8X-B5jfQRg-eMTs9Nbntr8=Mwbog@mail.gmail.com/T/
next prev parent reply other threads:[~2025-02-14 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 0:02 [RFC PATCH 0/4] ceph: fix generic/421 test failure Viacheslav Dubeyko
2025-02-05 0:02 ` [RFC PATCH 1/4] ceph: extend ceph_writeback_ctl for ceph_writepages_start() refactoring Viacheslav Dubeyko
2025-02-05 0:02 ` [RFC PATCH 2/4] ceph: introduce ceph_process_folio_batch() method Viacheslav Dubeyko
2025-02-05 0:02 ` [RFC PATCH 3/4] ceph: introduce ceph_submit_write() method Viacheslav Dubeyko
2025-02-14 21:11 ` Matthew Wilcox
2025-02-14 21:21 ` Viacheslav Dubeyko
2025-08-26 22:06 ` Max Kellermann
2025-08-26 22:33 ` Viacheslav Dubeyko
2025-08-26 22:53 ` Max Kellermann
2025-08-27 3:06 ` Viacheslav Dubeyko
2025-08-27 4:57 ` Max Kellermann
2025-02-05 0:02 ` [RFC PATCH 4/4] ceph: fix generic/421 test failure Viacheslav Dubeyko
2025-02-12 18:05 ` [RFC PATCH 0/4] " Viacheslav Dubeyko
2025-02-14 17:19 ` David Howells
2025-02-14 17:36 ` Viacheslav Dubeyko [this message]
2025-02-14 20:35 ` David Howells
2025-02-14 20:45 ` Viacheslav Dubeyko
2025-02-14 20:52 ` David Howells
2025-02-14 20:57 ` Viacheslav Dubeyko
2025-02-14 23:52 ` Viacheslav Dubeyko
2025-02-28 10:22 ` Christian Brauner
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=4e993d6ebadba1ed04261fd5590d439f382ca226.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pdonnell@redhat.com \
--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.