fsverity.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
	Andrey Albershteyn <aalbersh@redhat.com>,
	Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@infradead.org>,
	xfs <linux-xfs@vger.kernel.org>,
	Sweet Tea Dorminy <sweettea-kernel@dorminy.me>,
	Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	fsverity@lists.linux.dev, Eric Sandeen <sandeen@redhat.com>,
	Shirley Ma <shirley.ma@oracle.com>
Subject: Re: Handing xfs fsverity development back to you
Date: Fri, 21 Jun 2024 22:19:09 -0700	[thread overview]
Message-ID: <ZnZezSymGy2VyeeG@infradead.org> (raw)
In-Reply-To: <20240621172720.GD3058325@frogsfrogsfrogs>

On Fri, Jun 21, 2024 at 10:27:20AM -0700, Darrick J. Wong wrote:
> That sounds like a good approach for ext4 which will likely be feeding
> you folios from the pagecache anyway.  If Andrey sticks with the buffer
> cache that I wrote, then the virtual address is a slab allocation which
> is already mapped.

... yet another reasons to not be pointleslly different code and create
special cases and extra code in every layer of the stack..


      reply	other threads:[~2024-06-22  5:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 19:06 Handing xfs fsverity development back to you Darrick J. Wong
2024-06-17  9:34 ` Andrey Albershteyn
2024-06-21  4:35   ` Eric Biggers
2024-06-21 17:27     ` Darrick J. Wong
2024-06-22  5:19       ` Christoph Hellwig [this message]

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=ZnZezSymGy2VyeeG@infradead.org \
    --to=hch@infradead.org \
    --cc=aalbersh@redhat.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=shirley.ma@oracle.com \
    --cc=sweettea-kernel@dorminy.me \
    --cc=willy@infradead.org \
    /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).