From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Kanchan Joshi <joshi.k@samsung.com>,
Anuj Gupta <anuj20.g@samsung.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/5] generic: test I/O on devices with T10 protection information
Date: Mon, 24 Aug 2026 06:59:39 +0200 [thread overview]
Message-ID: <20260824045939.GC29550@lst.de> (raw)
In-Reply-To: <20260821233749.GG839663@frogsfrogsfrogs>
On Fri, Aug 21, 2026 at 04:37:49PM -0700, Darrick J. Wong wrote:
> > @@ -0,0 +1,91 @@
> > +#! /bin/bash
> > +# SPDX-License-Identifier: GPL-2.0
> > +# Copyright (c) 2026 Christoph Hellwig
> > +#
> > +# FS QA Test No. 2301
> > +#
> > +# Basix FSX sanity check when using T10 protection information
> > +#
> > +. ./common/preamble
> > +_begin_fstest auto rw pi dangerous
>
> Why dangerous? Can this crash the system?
Yes, the strip/insert case (which needs to be enabled through sysfs
crashes all release kernels up to and including 7.2.
next prev parent reply other threads:[~2026-08-24 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 5:11 add tests for file system on devices using protection information v2 Christoph Hellwig
2026-08-21 5:11 ` [PATCH 1/5] common/scsi_debug: don't slow down I/O Christoph Hellwig
2026-08-21 7:41 ` John Garry
2026-08-21 16:14 ` Bart Van Assche
2026-08-21 23:27 ` Darrick J. Wong
2026-08-24 4:58 ` Christoph Hellwig
2026-08-21 5:11 ` [PATCH 2/5] common: add a _sysfs_block_integrity_path helper Christoph Hellwig
2026-08-21 23:29 ` Darrick J. Wong
2026-08-24 4:58 ` Christoph Hellwig
2026-08-21 5:11 ` [PATCH 3/5] add a "pi" group Christoph Hellwig
2026-08-21 23:30 ` Darrick J. Wong
2026-08-21 5:11 ` [PATCH 4/5] generic: test I/O on devices with T10 protection information Christoph Hellwig
2026-08-21 23:37 ` Darrick J. Wong
2026-08-24 4:59 ` Christoph Hellwig [this message]
2026-08-21 5:11 ` [PATCH 5/5] generic: test corruption detection using " Christoph Hellwig
2026-08-21 23:38 ` Darrick J. Wong
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=20260824045939.GC29550@lst.de \
--to=hch@lst.de \
--cc=anuj20.g@samsung.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=zlang@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