From: Andrew Lunn <andrew@lunn.ch>
To: Leon Romanovsky <leon@kernel.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, "Ariel Almog" <ariela@nvidia.com>,
"Aditya Prabhune" <aprabhune@nvidia.com>,
"Hannes Reinecke" <hare@suse.de>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Arun Easi" <aeasi@marvell.com>,
"Jonathan Chocron" <jonnyc@amazon.com>,
"Bert Kenward" <bkenward@solarflare.com>,
"Matt Carlson" <mcarlson@broadcom.com>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Jean Delvare" <jdelvare@suse.de>,
"Alex Williamson" <alex.williamson@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"Jakub Kicinski" <kuba@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Stephen Hemminger" <stephen@networkplumber.org>
Subject: Re: [PATCH v4] PCI/sysfs: Change read permissions for VPD attributes
Date: Tue, 25 Feb 2025 18:30:25 +0100 [thread overview]
Message-ID: <7ff54e42-a76c-42b1-b95c-1dd2ee47fe93@lunn.ch> (raw)
In-Reply-To: <20250225165746.GH53094@unreal>
> We always read VPD by using "sudo ..." command, until one of our customers
> requested to provide a way to run monitoring library without any root access.
> It runs on hypervisor and being non-root there is super important for them.
You can chmod files in sys. So the administrator can change the
permissions, and then non-root users can access it.
This seems a more scalable solution that adding a special case in the
kernel.
Andrew
next prev parent reply other threads:[~2025-02-25 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 7:27 [PATCH v4] PCI/sysfs: Change read permissions for VPD attributes Leon Romanovsky
2025-02-25 16:05 ` Bjorn Helgaas
2025-02-25 16:57 ` Leon Romanovsky
2025-02-25 17:30 ` Andrew Lunn [this message]
2025-02-25 18:08 ` Leon Romanovsky
2025-02-25 18:59 ` Andrew Lunn
2025-02-25 20:05 ` Leon Romanovsky
2025-03-03 21:17 ` Bjorn Helgaas
2025-03-04 7:45 ` Leon Romanovsky
2025-03-05 14:58 ` Leon Romanovsky
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=7ff54e42-a76c-42b1-b95c-1dd2ee47fe93@lunn.ch \
--to=andrew@lunn.ch \
--cc=aeasi@marvell.com \
--cc=alex.williamson@redhat.com \
--cc=aprabhune@nvidia.com \
--cc=ariela@nvidia.com \
--cc=bkenward@solarflare.com \
--cc=hare@suse.de \
--cc=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jdelvare@suse.de \
--cc=jonnyc@amazon.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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