From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Lubomir Rintel <lrintel@redhat.com>,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>,
stable@vger.kernel.org
Subject: Re: [PATCH] usb-storage: Add max sectors quirk for Nokia 208
Date: Fri, 3 Jan 2025 08:12:28 +0100 [thread overview]
Message-ID: <2025010302-entering-paltry-bac5@gregkh> (raw)
In-Reply-To: <729d6c93-a794-4102-a191-494bf86df219@rowland.harvard.edu>
On Thu, Jan 02, 2025 at 11:22:00AM -0500, Alan Stern wrote:
> On Wed, Jan 01, 2025 at 10:22:06PM +0100, Lubomir Rintel wrote:
> > This fixes data corruption when accessing the internal SD card in mass
> > storage mode.
> >
> > I am actually not too sure why. I didn't figure a straightforward way to
> > reproduce the issue, but i seem to get garbage when issuing a lot (over 50)
> > of large reads (over 120 sectors) are done in a quick succession. That is,
> > time seems to matter here -- larger reads are fine if they are done with
> > some delay between them.
> >
> > But I'm not great at understanding this sort of things, so I'll assume
> > the issue other, smarter, folks were seeing with similar phones is the
> > same problem and I'll just put my quirk next to theirs.
> >
> > The "Software details" screen on the phone is as follows:
> >
> > V 04.06
> > 07-08-13
> > RM-849
> > (c) Nokia
> >
> > TL;DR version of the device descriptor:
> >
> > idVendor 0x0421 Nokia Mobile Phones
> > idProduct 0x06c2
> > bcdDevice 4.06
> > iManufacturer 1 Nokia
> > iProduct 2 Nokia 208
> >
> > The patch assumes older firmwares are broken too (I'm unable to test, but
> > no biggie if they aren't I guess), and I have no idea if newer firmware
> > exists.
> >
> > Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> > Cc: <stable@vger.kernel.org>
> > ---
>
> Hmmm, maybe we should automatically set this flag for all Nokia devices.
> In any case,
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> However, Greg's patch bot is going to ask why you didn't include a
> Fixes: tag.
No need for a Fixes: tag for a new quirk, what is odd is that this
didn't go through the linux-usb mailing list :(
I'll queue it up soon.
thanks,
greg k-h
prev parent reply other threads:[~2025-01-03 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 21:22 [PATCH] usb-storage: Add max sectors quirk for Nokia 208 Lubomir Rintel
2025-01-02 16:22 ` Alan Stern
2025-01-03 7:12 ` Greg Kroah-Hartman [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=2025010302-entering-paltry-bac5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=lrintel@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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