All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"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: Wed, 5 Mar 2025 16:58:41 +0200	[thread overview]
Message-ID: <20250305145841.GL1955273@unreal> (raw)
In-Reply-To: <20250304074512.GC1955273@unreal>

On Tue, Mar 04, 2025 at 09:45:12AM +0200, Leon Romanovsky wrote:
> On Mon, Mar 03, 2025 at 03:17:55PM -0600, Bjorn Helgaas wrote:
> > On Tue, Feb 25, 2025 at 10:05:49PM +0200, Leon Romanovsky wrote:
> > > On Tue, Feb 25, 2025, at 20:59, Andrew Lunn wrote:
> > > >> Chmod solution is something that I thought, but for now I'm looking
> > > >> for the out of the box solution. Chmod still require from
> > > >> administrator to run scripts with root permissions.
> > > >
> > > > It is more likely to be a udev rule. 
> > > 
> > > Udev rule is one of the ways to run such script.
> > > 
> > > > systemd already has lots of examples:
> > > >
> > > > /lib/udev/rules.d/50-udev-default.rules:KERNEL=="rfkill", MODE="0664"
> > 
> > Where are we at with this?  Is a udev rule a feasible solution?
> 
> We asked customer if this can work for him and still didn't get answer.
> I don't know if they have systemd/udev in their hypervisors.

We still didn't get any update, so let's drop this patch for now.

Thanks

> 
> Thanks
> 

      reply	other threads:[~2025-03-05 14:58 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
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 [this message]

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=20250305145841.GL1955273@unreal \
    --to=leon@kernel.org \
    --cc=aeasi@marvell.com \
    --cc=alex.williamson@redhat.com \
    --cc=andrew@lunn.ch \
    --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=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 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.