From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stuart Hayes <stuart.w.hayes@gmail.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scsi: target: Allow FUA if no write cache enabled
Date: Thu, 30 Apr 2026 11:43:38 -0400 [thread overview]
Message-ID: <yq1340cfogx.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260428203938.9738-1-stuart.w.hayes@gmail.com> (Stuart Hayes's message of "Tue, 28 Apr 2026 15:39:38 -0500")
Stuart,
> Without this patch, accesses with FUA set will be rejected, even
> though they always go directly to the media when there's no write
> cache.
The spec allows this. However, ...
> This is needed because EDK2 FAT filesystem code sets the FUA bit when
> writing, regardless of whether the device advertises support of
> DPOFUA.
^^^ that is clearly a spec violation. What is being done to address this
issue?
Also, wrt. the patch itself, please see:
https://sashiko.dev/#/patchset/20260428203938.9738-1-stuart.w.hayes%40gmail.com
--
Martin K. Petersen
prev parent reply other threads:[~2026-04-30 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 20:39 [PATCH v2] scsi: target: Allow FUA if no write cache enabled Stuart Hayes
2026-04-30 15:43 ` Martin K. Petersen [this message]
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=yq1340cfogx.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stuart.w.hayes@gmail.com \
--cc=target-devel@vger.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