From: Keith Busch <kbusch@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Konstantin Shelekhin <k.shelekhin@ftml.net>,
admin@aquinas.su, linux-bcachefs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
list-bcachefs@carlthompson.net, malte.schroeder@tnxip.de,
torvalds@linux-foundation.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17
Date: Tue, 12 Aug 2025 14:30:44 -0600 [thread overview]
Message-ID: <aJukdHj1CSzo6PmX@kbusch-mbp> (raw)
In-Reply-To: <htfkbxsxhdmojyr736qqsofghprpewentqzpatrvy4pytwublc@32aqisx4dlwj>
On Tue, Aug 12, 2025 at 04:03:17PM -0400, Kent Overstreet wrote:
> On Tue, Aug 12, 2025 at 01:35:56PM -0600, Keith Busch wrote:
> > On Mon, Aug 11, 2025 at 10:26:03AM -0400, Kent Overstreet wrote:
> > > On the other hand, for the only incidences I can remotely refer to in
> > > the past year and a half, there has been:
> > ...
> >
> > > - the block layer developer who went on a four email rant where he,
> > > charitably, misread the spec or the patchset or both; all this over a
> > > patch to simply bring a warning in line with the actual NVME and SCSI
> > > specs.
> >
> > Are you talking about this thread?
> >
> > https://lore.kernel.org/linux-block/20250311201518.3573009-14-kent.overstreet@linux.dev/
> >
> > I try to closely follow those lists, and that's the only thread I recall
> > that even slightly rings a bell from your description, however it's not
> > an accurate description (you were the one who misread the specs there; I
> > tried to help bridge the gap). I recall the interaction was pretty tame
> > though, so maybe you're talking about something else. Perhaps a link for
> > context if I got it wrong?
>
> I've since seen a lot of actual test data from SCSI hard drives - fua
> reads are definitely not cached, without exception across manufacturers.
>
> On NVME the situation is much murkier.
Okay, I take it I got the right thread then. I just wanted to get the
context. For the record, all the specs align with what read fua does
(anyone interested can visit the linked thread, I don't want to hijack
this one for it).
next prev parent reply other threads:[~2025-08-12 20:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:14 [GIT PULL] bcachefs changes for 6.17 Kent Overstreet
2025-08-05 21:19 ` Malte Schröder
2025-08-05 22:41 ` Carl E. Thompson
2025-08-07 12:42 ` Aquinas Admin
2025-08-09 17:36 ` Kent Overstreet
2025-08-09 19:21 ` Josef Bacik
2025-08-09 20:37 ` Kent Overstreet
2025-08-09 21:34 ` Kent Overstreet
2025-08-10 2:24 ` Theodore Ts'o
2025-08-10 3:17 ` Kent Overstreet
2025-08-10 4:05 ` Sasha Levin
2025-08-10 4:13 ` Kent Overstreet
2025-08-10 4:26 ` Gerald B. Cox
2025-08-10 5:17 ` Kent Overstreet
2025-08-10 5:59 ` Theodore Ts'o
2025-08-10 6:51 ` Kent Overstreet
2025-08-10 10:22 ` Martin Steigerwald
2025-08-11 15:48 ` Peanut gallery 2c James Lawrence
2025-08-11 16:08 ` Kent Overstreet
2025-08-11 17:00 ` James Lawrence
[not found] ` <aJsIOj6jbPKayO0s@mayhem.fritz.box>
2025-08-12 16:26 ` Kent Overstreet
2025-08-11 16:48 ` [GIT PULL] bcachefs changes for 6.17 Aquinas Admin
2025-08-10 8:02 ` Martin Steigerwald
2025-08-10 6:05 ` Carl E. Thompson
2025-08-11 16:02 ` Aquinas Admin
2025-08-11 16:09 ` Kent Overstreet
2025-08-09 23:01 ` Matthew Wilcox
2025-08-09 23:13 ` Kent Overstreet
2025-08-12 7:49 ` Jani Partanen
2025-08-12 10:09 ` Martin Steigerwald
2025-08-11 9:51 ` Konstantin Shelekhin
2025-08-11 14:26 ` Kent Overstreet
2025-08-11 18:13 ` Carl E. Thompson
2025-08-11 18:40 ` Malte Schröder
2025-08-12 0:44 ` Carl E. Thompson
2025-08-11 18:48 ` Aquinas Admin
2025-08-11 19:42 ` Martin Steigerwald
2025-08-11 21:04 ` Konstantin Shelekhin
2025-08-12 1:08 ` Kent Overstreet
2025-08-12 6:52 ` asdx
2025-08-12 7:04 ` Kent Overstreet
2025-08-12 7:17 ` asdx
2025-08-12 19:35 ` Keith Busch
2025-08-12 20:03 ` Kent Overstreet
2025-08-12 20:30 ` Keith Busch [this message]
2025-08-12 20:31 ` Kent Overstreet
2025-08-12 20:38 ` Keith Busch
2025-08-12 20:45 ` Kent Overstreet
2025-08-12 20:54 ` Keith Busch
2025-08-12 20:57 ` Kent Overstreet
2025-08-11 16:45 ` Aquinas Admin
2025-08-10 4:29 ` Gerhard Wiesinger
2025-08-07 14:27 ` Martin Steigerwald
2025-08-07 17:29 ` Peter Schneider
2025-08-10 6:20 ` Gerhard Wiesinger
2025-08-10 10:32 ` Martin Steigerwald
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=aJukdHj1CSzo6PmX@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=admin@aquinas.su \
--cc=k.shelekhin@ftml.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list-bcachefs@carlthompson.net \
--cc=malte.schroeder@tnxip.de \
--cc=torvalds@linux-foundation.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 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.