From: sashiko-bot@kernel.org
To: "Haruka Kuze" <harukak@zohomail.eu>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v2 1/2] rpmb: stop the routing after unregister
Date: Thu, 29 Oct 2026 12:47:28 +0000 [thread overview]
Message-ID: <sashiko-outbox-189308@kernel.org> (raw)
In-Reply-To: <20261029124132.2354314-2-harukak@zohomail.eu>
> From: Haruka Kuze <harukak@zohomail.eu>
>
> OP-TEE has a reference of RPMB device it used. So, it can route
> frames through the device after rpmb_dev_unregister() is called.
> Therefore, the parent device passed to route_frames() can be
> already freed, for example, mmc_blk_remove_rpmb_part() drops the
> last reference after rpmb unregister.
>
> This patch clears the route_frames when the device is going to
> be removed by getting new rwsem and makes rpmb_route_frames()
> return -ENODEV if the device is gone.
>
> Fixes: 1e9046e3a154 ("rpmb: add Replay Protected Memory Block (RPMB) subsystem")
> Assisted-by: LLM
> Signed-off-by: Haruka Kuze <harukak@zohomail.eu>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029124132.2354314-1-harukak@zohomail.eu?part=1
next prev parent reply other threads:[~2026-10-29 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 12:41 [PATCH v2 0/2] rpmb: add virtio RPMB driver Haruka Kuze
2026-10-29 12:41 ` Haruka Kuze via OP-TEE
2026-10-29 12:41 ` [PATCH v2 1/2] rpmb: stop the routing after unregister Haruka Kuze
2026-10-29 12:41 ` Haruka Kuze via OP-TEE
2026-10-29 12:47 ` sashiko-bot [this message]
2026-10-29 12:41 ` [PATCH v2 2/2] rpmb: add a virtio RPMB device driver Haruka Kuze
2026-10-29 12:41 ` Haruka Kuze via OP-TEE
2026-10-29 13:00 ` sashiko-bot
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=sashiko-outbox-189308@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=harukak@zohomail.eu \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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.