From: Ho Jie Feng <hjf3108@gmail.com>
To: Ulf Hansson <ulfh@kernel.org>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
Alex Dubov <oakad@yahoo.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ho Jie Feng <hjf3108@gmail.com>
Subject: [PATCH 0/5] memstick: fixes for mspro_block and ms_block
Date: Mon, 9 Nov 2026 23:34:40 +0800 [thread overview]
Message-ID: <20261109153510.7161-1-hjf3108@gmail.com> (raw)
This series fixes bugs that I found in the memstick core while writing
the bcm577x5_ms host driver for the Broadcom BCM57765/57785 card reader.
Some of these bugs were really rare, so I used Claude to automatically
fuzz access patterns/events to reproduce some of these issues.
Should I put this with Cc: stable?
Ho Jie Feng (5):
memstick: mspro_block: don't hand a finished request back to the host
memstick: mspro_block: wait for running dispatches in
mspro_block_stop()
memstick: ms_block: don't erase the old block of an unmapped LBA
memstick: ms_block: keep the power off during a full msb_reset()
memstick: ms_block: add the missing newline to the parallel switch
error
drivers/memstick/core/ms_block.c | 11 ++++++++---
drivers/memstick/core/mspro_block.c | 9 ++++++---
2 files changed, 14 insertions(+), 6 deletions(-)
base-commit: 461294b587f6fa5bb17d5856e4404b67d666086d
--
2.56.0
next reply other threads:[~2026-11-09 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:34 Ho Jie Feng [this message]
2026-11-09 15:38 ` [PATCH 1/5] memstick: mspro_block: don't hand a finished request back to the host Ho Jie Feng
2026-11-09 15:38 ` [PATCH 2/5] memstick: mspro_block: wait for running dispatches in mspro_block_stop() Ho Jie Feng
2026-11-09 15:38 ` [PATCH 3/5] memstick: ms_block: don't erase the old block of an unmapped LBA Ho Jie Feng
2026-11-09 15:38 ` [PATCH 4/5] memstick: ms_block: keep the power off during a full msb_reset() Ho Jie Feng
2026-11-09 15:38 ` [PATCH 5/5] memstick: ms_block: add the missing newline to the parallel switch error Ho Jie Feng
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=20261109153510.7161-1-hjf3108@gmail.com \
--to=hjf3108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=oakad@yahoo.com \
--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
all inboxes | Powered by JetHome®