From: Srinivas Kandagatla <srini@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>,
Johan Hovold <johan@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: linux-kernel@vger.kernel.org, brgl@kernel.org, stable@vger.kernel.org
Subject: Re: (subset) [PATCH v4 00/10] nvmem: rework nvmem core and allow unbinding with active consumers
Date: Sat, 30 May 2026 21:40:22 +0100 [thread overview]
Message-ID: <178017362283.116578.3318264066349893407.b4-ty@kernel.org> (raw)
In-Reply-To: <20260521-nvmem-unbind-v4-0-7fa136759491@oss.qualcomm.com>
On Thu, 21 May 2026 16:25:33 +0200, Bartosz Golaszewski wrote:
> Sashiko pointed out some issues so this iteration fixes them. I'm also
> Cc'ing Loic who seems to have encountered the issue of unbinding with
> active consumers when working on the block nvmem provider.
>
> Nvmem is one of the subsystems vulnerable to object life-time issues.
> The memory nvmem core dereferences is owned by nvmem providers which can
> be unbound at any time and even though nvmem devices themselves are
> reference-counted, there's no synchronization with the provider modules.
>
> [...]
Applied, thanks!
[01/10] nvmem: core: fix use-after-free bugs in error paths
commit: 034b31a7b03d5d0a0bf1ad67ccb84c2ddaddd7c2
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2026-05-30 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 14:25 Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 01/10] nvmem: core: fix use-after-free bugs in error paths Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 02/10] nvmem: remove unused field from struct nvmem_device Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 03/10] nvmem: return -EOPNOTSUPP to in-kernel users on missing callbacks Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 04/10] nvmem: check the return value of gpiod_set_value_cansleep() Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 05/10] nvmem: simplify locking with guard() Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 06/10] nvmem: remove unneeded __nvmem_device_put() Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 07/10] nvmem: split out the reg_read/write() callbacks out of struct nvmem_device Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 08/10] nvmem: simplify nvmem_sysfs_remove_compat() Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 09/10] nvmem: remove duplicated reference counting Bartosz Golaszewski
2026-05-21 14:25 ` [PATCH v4 10/10] nvmem: protect nvmem_device::ops with SRCU Bartosz Golaszewski
2026-05-30 20:40 ` Srinivas Kandagatla [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=178017362283.116578.3318264066349893407.b4-ty@kernel.org \
--to=srini@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=stable@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
all inboxes | Powered by JetHome®