From: Bart Van Assche <bvanassche@acm.org>
To: John Garry <john.g.garry@oracle.com>,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] scsi: scsi_debug: Remove sdebug_device_access_info
Date: Mon, 24 Feb 2025 10:04:29 -0800 [thread overview]
Message-ID: <e815bc89-269c-44fd-9f43-cd3389a137c7@acm.org> (raw)
In-Reply-To: <20250224115517.495899-2-john.g.garry@oracle.com>
On 2/24/25 3:55 AM, John Garry wrote:
> This structure is not used, so delete it.
>
> It was originally intended for supporting checking for atomic writes
> overlapping with ongoing reads and writes, but that support never got
> added.
>
> sbc-4 r22 section 4.29.3.2 "Performing operations during an atomic write
> operation" describes two methods of handling overlapping atomic writes.
> Currently the only method supported is for the ongoing read or write to
> complete.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2025-02-24 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 11:55 [PATCH 0/4] scsi_debug improvements John Garry
2025-02-24 11:55 ` [PATCH 1/4] scsi: scsi_debug: Remove sdebug_device_access_info John Garry
2025-02-24 18:04 ` Bart Van Assche [this message]
2025-02-24 11:55 ` [PATCH 2/4] scsi: scsi_debug: Remove a reference to in_use_bm John Garry
2025-02-24 11:55 ` [PATCH 3/4] scsi: scsi_debug: Simplify command handling John Garry
2025-02-24 11:55 ` [PATCH 4/4] scsi: scsi_debug: Do not sleep in atomic sections John Garry
2025-11-05 11:57 ` [PATCH] scsi: scsi_debug: make timeout faults by set delay to maximum value JiangJianJun
2025-11-05 12:00 ` JiangJianJun
2025-11-05 12:01 ` JiangJianJun
2025-11-05 11:54 ` John Garry
2025-11-06 12:03 ` JiangJianJun
2025-11-07 10:05 ` John Garry
2025-11-08 8:29 ` JiangJianJun
2025-11-08 9:38 ` John Garry
2025-11-11 10:59 ` JiangJianJun
2025-11-12 8:53 ` John Garry
2025-11-12 13:38 ` JiangJianJun
2025-11-12 16:02 ` John Garry
2025-11-13 11:22 ` JiangJianJun
2025-11-13 11:48 ` John Garry
2025-02-25 1:57 ` [PATCH 0/4] scsi_debug improvements Martin K. Petersen
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=e815bc89-269c-44fd-9f43-cd3389a137c7@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=john.g.garry@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox