From: Bjorn Helgaas <helgaas@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Leon Romanovsky" <leonro@nvidia.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, "Ariel Almog" <ariela@nvidia.com>,
"Aditya Prabhune" <aprabhune@nvidia.com>
Subject: Re: [PATCH] PCI/sysfs: Fix read permissions for VPD attributes
Date: Tue, 29 Oct 2024 19:04:50 -0500 [thread overview]
Message-ID: <20241030000450.GA1180398@bhelgaas> (raw)
In-Reply-To: <65791906154e3e5ea12ea49127cf7c707325ca56.1730102428.git.leonro@nvidia.com>
On Mon, Oct 28, 2024 at 10:05:33AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The Virtual Product Data (VPD) attribute is not readable by regular
> user without root permissions. Such restriction is not really needed,
> as data presented in that VPD is not sensitive at all.
>
> This change aligns the permissions of the VPD attribute to be accessible
> for read by all users, while write being restricted to root only.
>
> Cc: stable@vger.kernel.org
> Fixes: d93f8399053d ("PCI/sysfs: Convert "vpd" to static attribute")
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Applied to pci/vpd for v6.13, thanks!
> ---
> I added stable@ as it was discovered during our hardware ennoblement
> and it is important to be picked by distributions too.
> ---
> drivers/pci/vpd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/vpd.c b/drivers/pci/vpd.c
> index e4300f5f304f..2537685cac90 100644
> --- a/drivers/pci/vpd.c
> +++ b/drivers/pci/vpd.c
> @@ -317,7 +317,7 @@ static ssize_t vpd_write(struct file *filp, struct kobject *kobj,
>
> return ret;
> }
> -static BIN_ATTR(vpd, 0600, vpd_read, vpd_write, 0);
> +static BIN_ATTR_RW(vpd, 0);
>
> static struct bin_attribute *vpd_attrs[] = {
> &bin_attr_vpd,
> --
> 2.46.2
>
next prev parent reply other threads:[~2024-10-30 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 8:05 [PATCH] PCI/sysfs: Fix read permissions for VPD attributes Leon Romanovsky
2024-10-30 0:04 ` Bjorn Helgaas [this message]
2024-10-31 23:22 ` Bjorn Helgaas
2024-11-01 14:33 ` Leon Romanovsky
2024-11-01 16:47 ` Bjorn Helgaas
2024-11-03 12:33 ` Leon Romanovsky
2024-11-05 0:10 ` Bjorn Helgaas
2024-11-05 7:51 ` Leon Romanovsky
2024-11-05 15:24 ` Bjorn Helgaas
2024-11-05 16:26 ` Leon Romanovsky
2024-11-07 11:31 ` Leon Romanovsky
2024-11-07 14:59 ` Bjorn Helgaas
2024-11-07 16:15 ` 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=20241030000450.GA1180398@bhelgaas \
--to=helgaas@kernel.org \
--cc=aprabhune@nvidia.com \
--cc=ariela@nvidia.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-pci@vger.kernel.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