Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maurizio Lombardi <mlombard@redhat.com>
To: kbusch@kernel.org
Cc: linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de,
	dwagner@suse.de
Subject: [PATCH 2/2] nvme-pci: increase quirks_param buffer size to 256 bytes
Date: Fri, 23 Oct 2026 11:48:06 +0200	[thread overview]
Message-ID: <20261023094806.944563-3-mlombard@redhat.com> (raw)
In-Reply-To: <20261023094806.944563-1-mlombard@redhat.com>

The current 128 byte buffer for the nvme.quirks command line parameter
is a bit too small. If a user needs to specify multiple quirks or use
multiple VID:DID combinations, the configuration string can easily
exceed this limit.

Increase the size of the quirks_param array from 128 to 256 bytes to
comfortably accommodate longer and more complex quirk configurations.

Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
---
 drivers/nvme/host/pci.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 6699c7da4b5a..d6c8fcc6151a 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -232,7 +232,7 @@ static int quirks_param_set(const char *value, const struct kernel_param *kp)
 	return err;
 }
 
-static char quirks_param[128];
+static char quirks_param[256];
 static const struct kernel_param_ops quirks_param_ops = {
 	.set = quirks_param_set,
 	.get = param_get_string,
-- 
2.56.0



  parent reply	other threads:[~2026-10-23  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  9:48 [PATCH 0/2] Fix for nvme quirks module parameter Maurizio Lombardi
2026-10-23  9:48 ` [PATCH 1/2] nvme-pci: fix early boot hang with nvme.quirks parameter Maurizio Lombardi
2026-10-23  9:48 ` Maurizio Lombardi [this message]
2026-10-23 14:01 ` [PATCH 0/2] Fix for nvme quirks module parameter Laurence Oberman
2026-10-23 22:06 ` Keith Busch

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=20261023094806.944563-3-mlombard@redhat.com \
    --to=mlombard@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dwagner@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox