From: sashiko-bot@kernel.org
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/7] usb: storage: ene_ub6250: fix write to unmapped MS block
Date: Tue, 27 Oct 2026 14:51:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-186768@kernel.org> (raw)
In-Reply-To: <20261027-llm-usb-storage-v1-3-d1655e94ed10@linuxfoundation.org>
> From: Josef Bacik <josef@toxicpanda.com>
>
> Writing to a logical block of a Memory Stick that has no physical block
> assigned yet makes the ENE UB6250 driver write two bytes far past the
> end of its Phy2LogMap allocation.
>
> ms_scsi_write() looks up the current physical block of each logical
> block with ms_libconv_to_physical(). For a logical block that no
> physical block claimed during the scan, Log2PhyMap holds MS_LB_NOT_USED
> (0xffff), and for a logical block beyond NumberOfLogBlock the macro
> returns MS_STATUS_ERROR (0xfffe). After copying the data to the new
> block, the old one is marked as erased without any check:
>
> info->MS_Lib.Phy2LogMap[oldphy] = MS_LB_NOT_USED_ERASED;
>
> which, for those values, stores 0xfff5 about 128KiB past the start of
> an array that holds only NumberOfPhyBlock entries. Unassigned logical
> blocks are normal on a card that has not been completely written, and
> the card contents are under the control of whoever supplies the card
> or the reader.
>
> The bug was found by code inspection and has not been reproduced.
>
> Fix by only marking the old physical block as erased when it is a valid
> physical block number.
>
> Fixes: 33842cedfc33 ("Staging: Merge ENE UB6250 MS card codes from keucr to drivers/usb/storage/ene_ub6250.c")
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261027-llm-usb-storage-v1-0-d1655e94ed10@linuxfoundation.org?part=3
next prev parent reply other threads:[~2026-10-27 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:40 [PATCH 0/7] usb: storage: some llm-found patches Greg Kroah-Hartman
2026-10-27 14:40 ` [PATCH 1/7] usb: storage: ene_ub6250: fail MS init on card errors Greg Kroah-Hartman
2026-10-27 14:53 ` sashiko-bot
2026-10-27 14:40 ` [PATCH 2/7] usb: storage: ene_ub6250: report boot block errors Greg Kroah-Hartman
2026-10-27 14:53 ` sashiko-bot
2026-10-27 14:40 ` [PATCH 3/7] usb: storage: ene_ub6250: fix write to unmapped MS block Greg Kroah-Hartman
2026-10-27 14:51 ` sashiko-bot [this message]
2026-10-27 14:40 ` [PATCH 4/7] usb: storage: ene_ub6250: bound the disabled block walk Greg Kroah-Hartman
2026-10-27 14:52 ` sashiko-bot
2026-10-27 14:40 ` [PATCH 5/7] usb: storage: sddr09: bound the unused PBA search Greg Kroah-Hartman
2026-10-27 14:50 ` sashiko-bot
2026-10-27 14:40 ` [PATCH 6/7] usb: storage: shuttle_usbat: fix READ CD divide by zero Greg Kroah-Hartman
2026-10-27 14:51 ` sashiko-bot
2026-10-27 14:40 ` [PATCH 7/7] usb: storage: shuttle_usbat: bound the READ chunk size Greg Kroah-Hartman
2026-10-27 14:48 ` 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-186768@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox