linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: dhowells@redhat.com, "idryomov@gmail.com" <idryomov@gmail.com>,
	Alex Markuze <amarkuze@redhat.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:41:02 +0000	[thread overview]
Message-ID: <3669136.1738158062@warthog.procyon.org.uk> (raw)
In-Reply-To: <dbf086dc3113448cb4efaeee144ad01d39d83ea3.camel@ibm.com>

Viacheslav Dubeyko <Slava.Dubeyko@ibm.com> wrote:

> > Do you want me to push a branch with my tracepoints that I'm using somewhere
> > that you can grab it?
> 
> Sounds good! Maybe it can help me. :)

Take a look at:

   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/

The "ceph-folio" branch has Willy's folio conversion patches plus a tracing
patch plus a patch that's an unsuccessful attempt by me to fix the hang I was
seeing.

The tracepoint I'm using (netfs_folio) takes a folio pointer, so it was easier
to do it on top of Willy's patches.

The "netfs-crypto" branch are my patches to implement content crypto in
netfslib.  I've tested them to some extent with AFS, but the test code I have
in AFS only supports crypto of files where the file is an exact multiple of
page size as AFS doesn't support any sort of xattr and so I can't store the
real EOF pointer so simply.

The "ceph-iter" branch are my patches on top of a merge of those two
(excluding the debugging patches) to try and convert ceph to fully using
netfslib and to pass an iterator all the way down to the socket, aiming to
reduce the number of data types to basically two.

David


  parent reply	other threads:[~2025-01-29 13:41 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
2025-01-29 13:54             ` Alex Markuze
2025-01-29 13:41         ` David Howells [this message]
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=3669136.1738158062@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).