[GIT PULL] TPM DEVICE DRIVER: for-next-tpm-v7.3-rc6

[GIT PULL] TPM DEVICE DRIVER: for-next-tpm-v7.3-rc6

[Jarkko Sakkinen]

The following changes since commit 6f8319e3e9a44dd537d17f41565a8453c560a581:

  Merge tag 'mm-hotfixes-stable-2026-09-27-19-12' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-09-28 20:11:31 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/for-next-tpm-v7.3-rc6

for you to fetch changes up to 015fb29a748342a186f37b602ac70017098c8251:

  tpm: Disable TPM on null key name mismatch (2026-09-29 22:15:21 +0300)

----------------------------------------------------------------
Hi,

Please pull these bug fixes, which have landed after v7.3-rc1.

Br, Jarkko

----------------------------------------------------------------
Jiangshan Yi (3):
      tpm: Fix heap buffer overflow in tpm_transmit_cmd()
      tpm: Fix auth session leak in tpm2_get_random() error path
      tpm: fix off-by-four bounds check in tpm2_get_random()

Surendran Kanagaraj (1):
      tpm: Disable TPM on null key name mismatch

 drivers/char/tpm/tpm-interface.c | 2 +-
 drivers/char/tpm/tpm2-cmd.c      | 6 ++++--
 drivers/char/tpm/tpm2-sessions.c | 1 +
 3 files changed, 6 insertions(+), 3 deletions(-)

Re: [GIT PULL] TPM DEVICE DRIVER: for-next-tpm-v7.3-rc6

[Linus Torvalds]

On Thu, 1 Oct 2026 at 22:41, Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> Please pull these bug fixes, which have landed after v7.3-rc1.

Jarkko, I've asked you before: please write an explanation for your
pull requests.

"Please pull" is not a reason to pull. The "which landed after
v7.3-rc1" is also not talking about what they do.

The tag contains three lines of text, and none of those lines are in
the least helpful or relevant to the contents of the pull.

It doesn't have to be much. For simple driver fixes it can sometimes
be as trivial as just "Misc trivial fixes". But in this case it
clearly could have been something like "Fix tpm error handling and
buffer size bugs". Merge messages and pull requests  don't need the
_details_ - those are in the individual commits - but they should have
a high-level "what happened" overview.

And this pull request is actively hard to parse. The subject line says
"for-next". So I have to look at an email that is actively *trying* to
make it hard for me to decide whether I should pull and gives me *no*
information at all about what it contains.

Be better. Please.

                LInus

Re: [GIT PULL] TPM DEVICE DRIVER: for-next-tpm-v7.3-rc6

[pr-tracker-bot]

The pull request you sent on Fri, 2 Oct 2026 08:41:14 +0300:

> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/for-next-tpm-v7.3-rc6

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/17a58009754886eeacb9b826aa6d7bf5e294454d

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

Re: [GIT PULL] TPM DEVICE DRIVER: for-next-tpm-v7.3-rc6

[Jarkko Sakkinen]

On Fri, Oct 02, 2026 at 09:10:45AM -0700, Linus Torvalds wrote:
> On Thu, 1 Oct 2026 at 22:41, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > Please pull these bug fixes, which have landed after v7.3-rc1.
> 
> Jarkko, I've asked you before: please write an explanation for your
> pull requests.
> 
> "Please pull" is not a reason to pull. The "which landed after
> v7.3-rc1" is also not talking about what they do.
> 
> The tag contains three lines of text, and none of those lines are in
> the least helpful or relevant to the contents of the pull.

I do remember that you've said about this a few times. 

> 
> It doesn't have to be much. For simple driver fixes it can sometimes
> be as trivial as just "Misc trivial fixes". But in this case it
> clearly could have been something like "Fix tpm error handling and
> buffer size bugs". Merge messages and pull requests  don't need the
> _details_ - those are in the individual commits - but they should have
> a high-level "what happened" overview.

I meditated for a while before answering.

It's best to not do what I've done or try to fix it. Nothing works;
neither me nor the process...

I'll start faithfully writing cover letters progressively on side
while reviewing. That resolves about 75% of "what words to use"
and that type of stuff.

I mean I'm also right now zeroing my hard effort from code reviews
by not writing down the facts when they are still are fresh.

> 
> And this pull request is actively hard to parse. The subject line says
> "for-next". So I have to look at an email that is actively *trying* to
> make it hard for me to decide whether I should pull and gives me *no*
> information at all about what it contains.

I'll change it to:

"[GIT PULL] TPM DEVICE DRIVER changes for vX.Y.Z-rcW"

> 
> Be better. Please.
> 
>                 LInus

I'll do exactly what said above I will do, which I hope will equal to
that :-)

Br, Jarkko