Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Ao Sun <ao.sun@transsion.com>
To: "ulfh@kernel.org" <ulfh@kernel.org>,
	"avri.altman@sandisk.com" <avri.altman@sandisk.com>,
	"shawn.lin@rock-chips.com" <shawn.lin@rock-chips.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"jenswi@kernel.org" <jenswi@kernel.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hongyan Xia <hongyan.xia@transsion.com>,
	Ao Sun <ao.sun@transsion.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Jiazi Li <jiazi.li@transsion.com>
Subject: [PATCH v2] mmc: block: fix RPMB device unregister ordering
Date: Mon, 6 Jul 2026 11:43:00 +0000	[thread overview]
Message-ID: <20260706114218.907-1-ao.sun@transsion.com> (raw)

From: Ao Sun <ao.sun@transsion.com>

Since commit 7852028a35f0 ("mmc: block: register RPMB partition with
the RPMB subsystem"), each mmc RPMB partition is represented by two
device objects:
 - the mmc-owned device (`rpmb->dev`, backing the legacy /dev/mmcblkXrpmb
   char device) and
 - the rpmb-core device (`rdev`, backing /dev/rpmbN).

The child RPMB device holds a reference to its parent, so the 
parent's release callback cannot be invoked if the child device 
is still registered.

Remove rpmb_dev_unregister() from the parent release handler and 
unregister the child RPMB device in the remove path before tearing 
down the parent device.

Also delete the extra blank line between mmc_blk_remove_rpmb_part() 
and {.

Fixes: 7852028a35f0 ("mmc: block: register RPMB partition with the RPMB subsystem")
Cc: stable@vger.kernel.org
Signed-off-by: Jiazi Li <jiazi.li@transsion.com>
Signed-off-by: Ao Sun <ao.sun@transsion.com>
Reviewed-by: Avri Altman <avri.altman@sandisk.com>
---
Changes in v2:
  - add background describing the two RPMB device objects
  - add Fixes and Cc
  - collect Reviewed-by
---
 drivers/mmc/core/block.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
index 0274e8d07660..54a923ba4f1e 100644
--- a/drivers/mmc/core/block.c
+++ b/drivers/mmc/core/block.c
@@ -2715,7 +2715,6 @@ static void mmc_blk_rpmb_device_release(struct device *dev)
 {
 	struct mmc_rpmb_data *rpmb = dev_get_drvdata(dev);
 
-	rpmb_dev_unregister(rpmb->rdev);
 	mmc_blk_put(rpmb->md);
 	ida_free(&mmc_rpmb_ida, rpmb->id);
 	kfree(rpmb);
@@ -2930,8 +2929,8 @@ static int mmc_blk_alloc_rpmb_part(struct mmc_card *card,
 }
 
 static void mmc_blk_remove_rpmb_part(struct mmc_rpmb_data *rpmb)
-
 {
+	rpmb_dev_unregister(rpmb->rdev);
 	cdev_device_del(&rpmb->chrdev, &rpmb->dev);
 	put_device(&rpmb->dev);
 }
-- 
2.34.1


             reply	other threads:[~2026-07-06 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 11:43 Ao Sun [this message]
2026-07-06 15:47 ` [PATCH v2] mmc: block: fix RPMB device unregister ordering Ulf Hansson

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=20260706114218.907-1-ao.sun@transsion.com \
    --to=ao.sun@transsion.com \
    --cc=avri.altman@sandisk.com \
    --cc=beanhuo@micron.com \
    --cc=hongyan.xia@transsion.com \
    --cc=jenswi@kernel.org \
    --cc=jiazi.li@transsion.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=stable@vger.kernel.org \
    --cc=ulfh@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