All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org
Subject: scsi_debug: add support to corrupt data and/or reftag v3
Date: Mon, 31 Aug 2026 09:44:56 +0300	[thread overview]
Message-ID: <20260831064500.2576832-1-hch@lst.de> (raw)

This will be used for testing PI support in xfstests.

Sashiko complains about a few existing issues, and "duplicate"
existing issues because of the capacity wraparound.  I do not
plan to address them as the use case of wrap-around does not
overlap with this, and fixing it partially would be a mess.

Similarly the long non-preemptible sections if injecting a long
consecutive range of LBA are intentional, but probably a bad idea
for a user to perform.  But putting an abritrary limit on the
number of blocks would not be helpful either.

Changes since v2:
 - protect against fake_rw=1,

Changes since v1:
 - use match_int to parse the  reftag_adjust option
 - don't bypass error cleanup on parsing failure
 - allow to corrupt the entire capacity
 - set the bug_if_fake_rw to devip2sip to false
 - fix the check for unmapped LBAs
 - require DIX for reftag corruption injection
 - make the kernel messages a bit less verbose
 - add calls to sdeb_data_lock and sdeb_data_sector_lock

             reply	other threads:[~2026-08-31  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  6:44 Christoph Hellwig [this message]
2026-08-31  6:44 ` [PATCH] scsi_debug: add support to corrupt data and/or reftag Christoph Hellwig
2026-08-31  7:27   ` sashiko-bot

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=20260831064500.2576832-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.