All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <kch@nvidia.com>
To: <linux-block@vger.kernel.org>
Cc: <axboe@kernel.dk>, <kch@nvidia.com>,
	<damien.lemoal@opensource.wdc.com>, <johannes.thumshirn@wdc.com>,
	<ming.lei@redhat.com>, <bvanassche@acm.org>,
	<shinichiro.kawasaki@wdc.com>, <vincent.fu@samsung.com>
Subject: [PATCH V2 2/9] null_blk: check for valid submit_queue value
Date: Thu, 30 Mar 2023 14:31:27 -0700	[thread overview]
Message-ID: <20230330213134.131298-3-kch@nvidia.com> (raw)
In-Reply-To: <20230330213134.131298-1-kch@nvidia.com>

Right now we don't check for valid module parameter value for
submit_queue, that allows user to set negative values.

Add a callback null_set_submit_queues() to error out when submit_queue
value is < 1 before module is loaded.

Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
 drivers/block/null_blk/main.c | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
index cf6937f4cfa1..9e3df92d0b98 100644
--- a/drivers/block/null_blk/main.c
+++ b/drivers/block/null_blk/main.c
@@ -100,8 +100,18 @@ static int g_no_sched;
 module_param_named(no_sched, g_no_sched, int, 0444);
 MODULE_PARM_DESC(no_sched, "No io scheduler");
 
+static int null_set_submit_queues(const char *s, const struct kernel_param *kp)
+{
+	return null_param_store_int(s, kp->arg, 1, INT_MAX);
+}
+
+static const struct kernel_param_ops null_submit_queues_param_ops = {
+	.set	= null_set_submit_queues,
+	.get	= param_get_int,
+};
+
 static int g_submit_queues = 1;
-module_param_named(submit_queues, g_submit_queues, int, 0444);
+device_param_cb(submit_queues, &null_submit_queues_param_ops, &g_submit_queues, 0444);
 MODULE_PARM_DESC(submit_queues, "Number of submission queues");
 
 static int g_poll_queues = 1;
-- 
2.29.0


  parent reply	other threads:[~2023-03-30 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 21:31 [PATCH V2 0/9] null_blk: add modparam checks Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 1/9] null_blk: adjust null_param_store_val() Chaitanya Kulkarni
2023-03-30 21:31 ` Chaitanya Kulkarni [this message]
2023-03-30 21:31 ` [PATCH V2 3/9] null_blk: check for valid poll_queue value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 4/9] null_blk: check for valid gb value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 5/9] null_blk: check for valid block size value Chaitanya Kulkarni
2023-03-30 22:45   ` Damien Le Moal
2023-03-30 22:52     ` Chaitanya Kulkarni
2023-03-30 22:59       ` Damien Le Moal
2023-03-30 21:31 ` [PATCH V2 6/9] null_blk: check for valid max_sectors value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 7/9] null_blk: check for valid queue depth value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 8/9] null_blk: avoid use global modparam g_queue_mode Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 9/9] null_blk: avoid use global modparam g_irq_mode Chaitanya Kulkarni
2023-03-30 23:02 ` [PATCH V2 0/9] null_blk: add modparam checks Jens Axboe
2023-03-31  4:52   ` Chaitanya Kulkarni

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=20230330213134.131298-3-kch@nvidia.com \
    --to=kch@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=vincent.fu@samsung.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 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.