Re: [PATCH v2 1/2] tpm: Track the response read position internally
From: Rustam Mustafin
Date: Fri Nov 20 2026 - 09:29:15 EST
On Fri, Nov 20, 2026 at 7:27 PM Jarkko Sakkinen <jarkko@xxxxxxxxxx> wrote:
> On Fri, Nov 20, 2026 at 07:16:13PM +0700, Rustam Mustafin wrote:
[...]
> So... why does not this block uring? You are implementing a feature
> as a bug fix, or so that it appears.
Patch 1 also fixes a plain read() racing a write() (the second trace),
which does not involve io_uring, so blocking io_uring alone would not
cover it. Patch 1 is small, so it might be easier to backport.
The io_uring block is posted on top of this series:
https://lore.kernel.org/all/20261120142116.1630010-1-rmustafin@xxxxxxxxxxxxxx/
It depends on this series, because the new ->read_iter() would let
vfs_iter_read() callers such as Coda reach tpm_common_read() with
their own offset.
Br,
Rustam