From: srini@kernel.org
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Srinivas Kandagatla <srini@kernel.org>
Subject: [PATCH 0/2] nvmem: fixes for 7.1
Date: Sat, 30 May 2026 21:43:38 +0100 [thread overview]
Message-ID: <20260530204340.116743-1-srini@kernel.org> (raw)
From: Srinivas Kandagatla <srini@kernel.org>
Hi Greg,
Here are some fixes in nvmem which can go for 7.1 release
Could you please queue these as 7.1 material.
Fixes include
- a use-after fix bug fix
- fix hang in onie-tlv
Thanks for all the help,
Srini
Andre Heider (1):
nvmem: layouts: onie-tlv: fix hang on unknown types
Bartosz Golaszewski (1):
nvmem: core: fix use-after-free bugs in error paths
drivers/nvmem/core.c | 12 +++++-------
drivers/nvmem/layouts/onie-tlv.c | 3 ++-
2 files changed, 7 insertions(+), 8 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-30 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 20:43 srini [this message]
2026-05-30 20:43 ` [PATCH 1/2] nvmem: layouts: onie-tlv: fix hang on unknown types srini
2026-05-30 20:43 ` [PATCH 2/2] nvmem: core: fix use-after-free bugs in error paths srini
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=20260530204340.116743-1-srini@kernel.org \
--to=srini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox