From: Finn Thain <fthain@linux-m68k.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Chengfeng Ye <dg573847474@gmail.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Jack Wang <jinpu.wang@cloud.ionos.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: pm8001: Fix potential TOCTOU race in pm8001_find_tag
Date: Wed, 21 Jan 2026 10:43:12 +1100 (AEDT) [thread overview]
Message-ID: <2f7c49e3-302c-30d5-63ac-29412f3c6ed5@linux-m68k.org> (raw)
In-Reply-To: <b03e802fce29c90bbc4342e7254c3adb9f48bbf7.camel@HansenPartnership.com>
On Tue, 20 Jan 2026, James Bottomley wrote:
>
> But this too is a problem: fixes aren't free. In fact a portion of the
> patches sold as a bug fix eventually turn out to introduce a bug ... and
> that new bug is one we didn't have before. This is just a sad
> consequence of the fact that all code produced by humans contains bugs.
Yes. And if the shiny new tool has agency inasmuchas it tests patches in
emulators, then the code produced by the new tool will also contain bugs.
Perhaps there are cycle-accurate, hardware-bug-compatible emulators for a
few hardware designs. But asserting the correctness (hardware-equivalence)
of such emulators runs into the very same problem.
So, unless tested on suitable hardware, one might expect driver patch
submissions to be rejected with little or no review.
prev parent reply other threads:[~2026-01-20 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 10:19 Chengfeng Ye
2026-01-18 9:42 ` Markus Elfring
2026-01-19 15:24 ` Chengfeng Ye
2026-01-19 16:39 ` James Bottomley
2026-01-19 16:50 ` Chengfeng Ye
2026-01-20 3:42 ` James Bottomley
2026-01-20 4:39 ` Chengfeng Ye
2026-01-20 14:28 ` James Bottomley
2026-01-20 16:39 ` Chengfeng Ye
2026-01-20 23:43 ` Finn Thain [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=2f7c49e3-302c-30d5-63ac-29412f3c6ed5@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dg573847474@gmail.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®