Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Anuj Gupta <anuj20.g@samsung.com>,
	John Garry <john.g.garry@oracle.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 5/6] generic: test I/O on devices with T10 protection information
Date: Mon, 7 Sep 2026 07:48:46 +0200	[thread overview]
Message-ID: <20260907054846.GB31481@lst.de> (raw)
In-Reply-To: <bd707d1a-3af1-4d1d-b6da-ac676a9c666d@samsung.com>

On Tue, Sep 01, 2026 at 12:08:59PM +0530, Kanchan Joshi wrote:
> On 8/31/2026 12:15 PM, Christoph Hellwig wrote:
> > +test_dif()
> > +{
> > +	local pi_type=$1
> > +	local pi_enable="$2"
> > +
> > +	scsi_debug_pi_opts="write_same_length=0 dif=${pi_type} dix=1"
> > +	SCSI_DEBUG_DEV=`_get_scsi_debug_dev 512 512 0 $size $scsi_debug_pi_opts`
> > +
> > +	SCSI_DEBUG_MNT="$TEST_DIR/scsi_debug_$seq"
> > +	rm -rf $SCSI_DEBUG_MNT
> > +	mkdir $SCSI_DEBUG_MNT
> > +
> > +	_mkfs_dev $SCSI_DEBUG_DEV || \
> > +		_fail "Can't make $FSTYP on DIF-enabled scsi_debug device"
> > +	run_check _mount $SCSI_DEBUG_DEV $SCSI_DEBUG_MNT
> > +	bsize=$($here/src/min_dio_alignment $SCSI_DEBUG_MNT $SCSI_DEBUG_DEV)
> 
> bsize remains unused.

_run_fsx uses it through the (somewhat odd) BSIZE substitution.

> dio_opts is unused.

Yeah.

> 
> > +	fsx_run -N 10000            -l 500000 -r BSIZE -w BSIZE -Z -R -W
> 
> Is passing BSIZE correct?

See above :)

  reply	other threads:[~2026-09-07  5:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  6:45 add tests for file system on devices using protection information v3 Christoph Hellwig
2026-08-31  6:45 ` [PATCH 1/6] common/scsi_debug: don't slow down I/O Christoph Hellwig
2026-08-31  6:45 ` [PATCH 2/6] common: factor out a _bdev_disk_name helper Christoph Hellwig
2026-08-31 17:03   ` Darrick J. Wong
2026-08-31  6:45 ` [PATCH 3/6] common: add a _sysfs_block_integrity_path helper Christoph Hellwig
2026-08-31 17:03   ` Darrick J. Wong
2026-08-31  6:45 ` [PATCH 4/6] add a "pi" group Christoph Hellwig
2026-08-31  6:45 ` [PATCH 5/6] generic: test I/O on devices with T10 protection information Christoph Hellwig
2026-09-01  6:38   ` Kanchan Joshi
2026-09-07  5:48     ` Christoph Hellwig [this message]
2026-09-03  6:01   ` Anuj Gupta/Anuj Gupta
2026-08-31  6:45 ` [PATCH 6/6] generic: test corruption detection using " Christoph Hellwig
2026-09-03  6:00   ` Anuj Gupta/Anuj Gupta
2026-09-07  5:49     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2026-09-07  7:58 add tests for file system on devices using protection information v4 Christoph Hellwig
2026-09-07  7:58 ` [PATCH 5/6] generic: test I/O on devices with T10 protection information Christoph Hellwig
2026-09-08 14:33   ` Kanchan Joshi
2026-09-11  7:08 add tests for file system on devices using protection information v5 Christoph Hellwig
2026-09-11  7:08 ` [PATCH 5/6] generic: test I/O on devices with T10 protection information 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=20260907054846.GB31481@lst.de \
    --to=hch@lst.de \
    --cc=anuj20.g@samsung.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=john.g.garry@oracle.com \
    --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