From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 219027] The SCSI can't adjust Max xfer length (blocks) with different storage device
Date: Tue, 23 Jul 2024 01:57:05 +0000 [thread overview]
Message-ID: <bug-219027-11613-LLWhFYpd9s@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219027-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219027
--- Comment #3 from LXY (983292588@qq.com) ---
(In reply to Martin K. Petersen from comment #1)
> Due to some legacy devices hanging when probing for non-existent pages the
> Linux USB storage driver opts out of consulting the Block Limits VPD.
>
> I suggest you create a udev rule to override
> /sys/block/sdN/queue/max_sectors_kb.
Thanks for your reply.
I've tried creating udev rules and it works. But whenever I use my USB storage
device on a new PC, I find it a little inconvenient to create rules.
So I'm trying to find a way to get Linux PC consulting the Block Limits VPD. Do
you mean that for all Linux USB storage drivers, Linux hosts will not consult
the Block Limits VPD?
I actually have the firmware source code for my USB storage device, and I can
make some changes I want. For example, change the VPD page it supports. Do you
think it will work?
Best wishes.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-07-23 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 2:21 [Bug 219027] New: The SCSI can't adjust Max xfer length (blocks) with different storage device bugzilla-daemon
2024-07-23 1:10 ` [Bug 219027] " bugzilla-daemon
2024-07-23 1:56 ` bugzilla-daemon
2024-07-23 1:57 ` bugzilla-daemon [this message]
2024-08-04 4:38 ` bugzilla-daemon
2024-08-05 12:46 ` bugzilla-daemon
2024-08-05 19:28 ` bugzilla-daemon
2024-08-06 2:16 ` bugzilla-daemon
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=bug-219027-11613-LLWhFYpd9s@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.