linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: Eric Biggers <ebiggers@kernel.org>
Cc: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
	linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v5 0/4] tests for btrfs fsverity
Date: Tue, 8 Feb 2022 14:34:45 -0800	[thread overview]
Message-ID: <YgLwBeFkkYK15j1+@zen> (raw)
In-Reply-To: <YgHTeMETyYlatbuM@sol.localdomain>

On Mon, Feb 07, 2022 at 06:20:40PM -0800, Eric Biggers wrote:
> On Mon, Sep 13, 2021 at 11:44:33AM -0700, Boris Burkov wrote:
> > This patchset provides tests for fsverity support in btrfs.
> > 
> > It includes modifications for generic tests to pass with btrfs as well
> > as new tests.
> > 
> 
> Hi Boris, there's been no activity on this patchset in a while.  Are you
> planning to keep working on it?  I'd like to see it finished so that I can start
> including btrfs in the fs-verity testing I do.

Hi Eric,

Sorry for not following through on this. I just lost momentum and got
carried off focusing on other more pressing things. I do want to get
this (and the verity kill-switch I started and abandoned...) in, and
will make time to do so soon.

Hopefully this week, but if not, then definitely next week.

Thanks for following up,
Boris

> 
> - Eric

      reply	other threads:[~2022-02-08 23:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 18:44 [PATCH v5 0/4] tests for btrfs fsverity Boris Burkov
2021-09-13 18:44 ` [PATCH v5 1/4] btrfs: test btrfs specific fsverity corruption Boris Burkov
2021-09-13 18:44 ` [PATCH v5 2/4] generic/574: corrupt btrfs merkle tree data Boris Burkov
2021-09-13 18:44 ` [PATCH v5 3/4] btrfs: test verity orphans with dmlogwrites Boris Burkov
2021-09-13 18:44 ` [PATCH v5 4/4] generic: test fs-verity EFBIG scenarios Boris Burkov
2021-09-16 21:18   ` Eric Biggers
2022-02-08  2:20 ` [PATCH v5 0/4] tests for btrfs fsverity Eric Biggers
2022-02-08 22:34   ` Boris Burkov [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=YgLwBeFkkYK15j1+@zen \
    --to=boris@bur.io \
    --cc=ebiggers@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.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).