From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <axboe@kernel.dk>
Cc: <hch@lst.de>, <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCHv4 0/2] block: don't forget user settings
Date: Thu, 5 Jan 2023 12:51:44 -0800 [thread overview]
Message-ID: <20230105205146.3610282-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
If the user overrides the max sectors for their device (which is
currently defaulting to quite a low value for modern hardware), their
request is lost on a rescan. Save it and fix the weird type issues.
Changes since v3: Fixed the unsigned long/unsigned int issue raised by
clang.
Keith Busch (2):
block: make BLK_DEF_MAX_SECTORS unsigned
block: save user max_sectors limit
Documentation/ABI/stable/sysfs-block | 3 ++-
block/blk-settings.c | 9 +++++++--
block/blk-sysfs.c | 21 +++++++++++++++------
drivers/block/null_blk/main.c | 3 +--
include/linux/blkdev.h | 4 +++-
5 files changed, 28 insertions(+), 12 deletions(-)
--
2.30.2
next reply other threads:[~2023-01-05 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 20:51 Keith Busch [this message]
2023-01-05 20:51 ` [PATCHv4 1/2] block: make BLK_DEF_MAX_SECTORS unsigned Keith Busch
2023-01-05 21:19 ` Bart Van Assche
2023-01-08 17:13 ` Christoph Hellwig
2023-01-09 0:23 ` Martin K. Petersen
2023-01-05 20:51 ` [PATCHv4 2/2] block: save user max_sectors limit Keith Busch
2023-01-05 21:28 ` Bart Van Assche
2023-01-05 21:36 ` Keith Busch
2023-01-08 17:13 ` Christoph Hellwig
2023-01-09 0:25 ` Martin K. Petersen
2023-01-09 3:27 ` [PATCHv4 0/2] block: don't forget user settings Jens Axboe
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=20230105205146.3610282-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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