From: <shao.mingyin@zte.com.cn>
To: <bvanassche@acm.org>
Cc: <martin.petersen@oracle.com>, <alim.akhtar@samsung.com>,
<james.bottomley@hansenpartnership.com>,
<peter.griffin@linaro.org>, <beanhuo@micron.com>,
<stanleyjhu@google.com>, <linux-scsi@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 0/2] scsi: ufs: fix an RPMB teardown cycle and a shift UB
Date: Wed, 4 Nov 2026 03:00:52 +0800 (CST) [thread overview]
Message-ID: <20261104030052059PG6LDNeanA7C3vQaZAOff@zte.com.cn> (raw)
In-Reply-To: <4f38227c-a524-4d42-a3e4-ad0157939b41@acm.org>
On 11/3/26 09:51, Bart Van Assche wrote:
> This series no longer applies. Please rebase it on top of Martin's
> for-next branch.
Done, thanks. The problem was the base-commit: v1 was generated against
linux-next next-20261030 (7649ba73f9e7), which is not an ancestor of
for-next, so b4 refused to apply it.
I rebased both patches onto for-next (v7.4-rc1, 6628e7d4c6b2) and resent
them as v2:
https://lore.kernel.org/all/202611040259247915t_cYYK0k5pPbEqfdTAQu@zte.com.cn/
The hunks are unchanged. While testing patch 1 I also confirmed that the
teardown path only becomes reachable once the "scsi: ufs: rpmb: register
and unregister the ufs_rpmb bus" patch lands: without it device_register()
fails with -EINVAL. On top of that patch, a synthetic hba on QEMU shows
the rpmb0 class device surviving ufs_rpmb_remove() before the fix and
disappearing after it.
Thanks,
Shao
prev parent reply other threads:[~2026-11-03 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 10:52 shao.mingyin
2026-11-03 10:52 ` [PATCH 1/2] scsi: ufs: core: unregister RPMB devices before their parent shao.mingyin
2026-11-03 10:52 ` [PATCH 2/2] scsi: ufs: exynos: use BIT() for the nexus type tag mask shao.mingyin
2026-11-03 17:51 ` [PATCH 0/2] scsi: ufs: fix an RPMB teardown cycle and a shift UB Bart Van Assche
2026-11-03 19:00 ` shao.mingyin [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=20261104030052059PG6LDNeanA7C3vQaZAOff@zte.com.cn \
--to=shao.mingyin@zte.com.cn \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.griffin@linaro.org \
--cc=stable@vger.kernel.org \
--cc=stanleyjhu@google.com \
/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®