Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Maurizio Lombardi <mlombard@bsdbackstore.eu>,
	Bart Van Assche <bvanassche@acm.org>,
	Maurizio Lombardi <mlombard@redhat.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>
Cc: "bgurney@redhat.com" <bgurney@redhat.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: expose active quirks in sysfs
Date: Wed, 29 Oct 2025 05:47:50 +0000	[thread overview]
Message-ID: <08f479ed-9817-4806-bf68-c929c8a844a6@nvidia.com> (raw)
In-Reply-To: <DDU46S76MOXJ.XX5QODFDZTZN@bsdbackstore.eu>

On 10/28/25 10:00, Maurizio Lombardi wrote:
> On Tue Oct 28, 2025 at 5:32 PM CET, Bart Van Assche wrote:
>> On 10/28/25 7:29 AM, Maurizio Lombardi wrote:
>>> Currently, there is no straightforward way for a user to inspect
>>> the quirks value from userspace.
>>> Add a new read-only sysfs attribute "quirks";
>>> reading this file will display the hexadecimal
>>> value of the ctrl->quirks bitmask for the given NVMe device.
>> This patch changes the constants in enum nvme_quirks from
>> kernel-internal constants into an ABI. I'm not sure that's what we
>> want.
> I understand your concern.
> I could respin it to export the names of the active quirks
> rather than the raw bitmask, if there is an interest in having
> this feature.
>
> Maurizio
>
question here: do we need to care about some kind of security before we 
expose controller information that is internal to the driver ? 
CAP_SYS_ADMIN ? -ck


  reply	other threads:[~2025-10-29  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 14:29 [PATCH] nvme-pci: expose active quirks in sysfs Maurizio Lombardi
2025-10-28 16:32 ` Bart Van Assche
2025-10-28 17:00   ` Maurizio Lombardi
2025-10-29  5:47     ` Chaitanya Kulkarni [this message]
2025-10-29  8:02       ` Maurizio Lombardi
2025-10-29 23:25         ` Chaitanya Kulkarni
2025-10-30  6:18           ` Maurizio Lombardi
2025-10-30  6:46             ` Chaitanya Kulkarni
2025-10-30  6:55               ` Maurizio Lombardi
2025-10-30  6:57                 ` Maurizio Lombardi

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=08f479ed-9817-4806-bf68-c929c8a844a6@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=bgurney@redhat.com \
    --cc=bvanassche@acm.org \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@bsdbackstore.eu \
    --cc=mlombard@redhat.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