From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, ebiggers@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] generic: test that truncate(2) on fsverity is blocked
Date: Thu, 22 Jan 2026 06:59:08 +0100 [thread overview]
Message-ID: <20260122055908.GB23964@lst.de> (raw)
In-Reply-To: <20260121150833.shad4rfhqd4deg2s@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Wed, Jan 21, 2026 at 11:08:33PM +0800, Zorro Lang wrote:
> > + dio-writeback-race unlink-fsync truncate
>
> Need to add this into .gitignore too :)
True.
> > +_require_test
>
> Does this case need TEST_DEV and TEST_DIR?
No, just copied and pasted.
> > +$here/src/truncate $fsv_file
>
> _require_test_program "truncate"
Ok.
next prev parent reply other threads:[~2026-01-22 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 6:24 [PATCH] generic: test that truncate(2) on fsverity is blocked Christoph Hellwig
2026-01-21 15:08 ` Zorro Lang
2026-01-22 5:59 ` Christoph Hellwig [this message]
2026-01-22 7:23 ` Zorro Lang
2026-01-22 7:25 ` Christoph Hellwig
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=20260122055908.GB23964@lst.de \
--to=hch@lst.de \
--cc=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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