Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Arbab Haider <arbabhaider649@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Shichao Lai <shichaorai@gmail.com>,
	linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
	linux-kernel@vger.kernel.org,
	syzbot+dc208a8cf8d37cf3e5ac@syzkaller.appspotmail.com,
	stable@vger.kernel.org, Arbab Haider <arbabhaider649@gmail.com>
Subject: Re: [PATCH] usb-storage: alauda: track media_initialized per port
Date: Sun, 22 Nov 2026 13:05:51 +0500	[thread overview]
Message-ID: <20261122080550.2181-2-arbabhaider649@gmail.com> (raw)
In-Reply-To: <5d2e1310-88db-427e-ace0-c2a0590560b1@rowland.harvard.edu>

On Sat, Nov 21, 2026 at 03:54:57PM -0500, Alan Stern wrote:
> Has this patch been tested?

Yes, tested in QEMU (x86_64, v7.4-rc3 with KASAN, UBSAN, dummy_hcd,
raw_gadget, and usb-storage alauda enabled). I do not have physical
Alauda hardware, so testing was done via dummy_hcd + raw_gadget:

- Before the patch: running the syzbot C reproducer reproduced the
  UBSAN division-overflow / divide error in alauda_read_data()
  (drivers/usb/storage/alauda.c:986) on LUN 1.

- After the patch: the syzbot reproducer passes with no UBSAN, KASAN,
  or divide errors. I also verified additional raw_gadget scenarios:
  * READ_CAPACITY and READ_10 on both LUN 0 and LUN 1
  * Media removal (status 0x80) followed by re-insertion without the
    0x08 media-change bit and READ_10
  * Media change with a failing alauda_init_media() (unrecognized media
    signature) followed by READ_10 and WRITE_10
  * Recovery back to a valid media signature with TEST_UNIT_READY,
    READ_CAPACITY, and READ_10

Regards,
Arbab

      reply	other threads:[~2026-11-22  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21 17:19 [PATCH] usb-storage: alauda: track media_initialized per port Arbab Haider
2026-11-21 20:54 ` Alan Stern
2026-11-22  8:05   ` Arbab Haider [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=20261122080550.2181-2-arbabhaider649@gmail.com \
    --to=arbabhaider649@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shichaorai@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+dc208a8cf8d37cf3e5ac@syzkaller.appspotmail.com \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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