From: Jarkko Sakkinen <jarkko@kernel.org>
To: Rustam Mustafin <rmustafin@cloudlinux.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Shuah Khan <shuah@kernel.org>, Jaewon Yang <yong010301@gmail.com>,
linux-integrity@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] tpm: Track the response read position internally
Date: Fri, 20 Nov 2026 16:50:44 +0200 [thread overview]
Message-ID: <awBeRE2c7UQH8SfV@kernel.org> (raw)
In-Reply-To: <CAG6=z5tzc8DG-7gU03mKs1JxqEzUULwBinfHKtYWyPycKkG6mA@mail.gmail.com>
On Fri, Nov 20, 2026 at 09:28:53PM +0700, Rustam Mustafin wrote:
> On Fri, Nov 20, 2026 at 7:27 PM Jarkko Sakkinen <jarkko@kernel.org> 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@cloudlinux.com/
>
> 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.
My mishap.
Sorry. I'll look into this soon.
>
> Br,
> Rustam
Br, Jarkko
next prev parent reply other threads:[~2026-11-20 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 12:16 [PATCH v2 0/2] tpm: Track the response read position internally Rustam Mustafin
2026-11-20 12:16 ` [PATCH v2 1/2] " Rustam Mustafin
2026-11-20 12:27 ` Jarkko Sakkinen
2026-11-20 14:28 ` Rustam Mustafin
2026-11-20 14:50 ` Jarkko Sakkinen [this message]
2026-11-20 12:16 ` [PATCH v2 2/2] selftests: tpm2: test that io_uring reads ignore the file offset Rustam Mustafin
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=awBeRE2c7UQH8SfV@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rmustafin@cloudlinux.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yong010301@gmail.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 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.