From: Brian Norris <briannorris@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: bhelgaas@google.com, stable-commits@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: Patch "PCI/sysfs: Ensure devices are powered for config reads" has been added to the 6.6-stable tree
Date: Mon, 20 Oct 2025 13:44:02 -0700 [thread overview]
Message-ID: <aPafEhXHnbLp_esg@google.com> (raw)
In-Reply-To: <aPKB8V3NTeqcXCzu@google.com>
On Fri, Oct 17, 2025 at 10:50:43AM -0700, Brian Norris wrote:
> On Fri, Oct 17, 2025 at 08:58:20AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Oct 16, 2025 at 08:15:46AM -0700, Brian Norris wrote:
> > > If adapting this change to pre-commit-d2bd39c0456b is better, I can
> > > submit an updated version here.
> > >
> > > Without commit d2bd39c0456b, it just means that the 'max_link_speed'
> > > sysfs attribute is still susceptible to accessing a powered-down
> > > device/link. We're in no worse state than we were without this patch.
> > > And frankly, people are not likely to notice if they haven't already,
> > > since I'd guess most systems don't suspend devices this aggressively.
> >
> > I'll gladly accept a fixed up patch for this, thanks.
>
> I'll try to get that out today.
I didn't make time on Friday, and this patch was committed to 6.6.y
already. So I've submitted a "part 2" here:
Subject: [PATCH 6.6] PCI/sysfs: Ensure devices are powered for config reads (part 2)
https://lore.kernel.org/all/20251020204146.3193844-1-briannorris@chromium.org/
Brian
prev parent reply other threads:[~2025-10-20 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025101627-purifier-crewless-0d52@gregkh>
2025-10-16 15:15 ` Patch "PCI/sysfs: Ensure devices are powered for config reads" has been added to the 6.6-stable tree Brian Norris
2025-10-17 6:58 ` Greg KH
2025-10-17 17:50 ` Brian Norris
2025-10-20 20:44 ` Brian Norris [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=aPafEhXHnbLp_esg@google.com \
--to=briannorris@chromium.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 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.