From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Pali Rohár" <pali@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: PCI: Race condition in pci_create_sysfs_dev_files (can't boot)
Date: Mon, 31 Jan 2022 12:56:18 +0100 [thread overview]
Message-ID: <m38ruwxgnx.fsf@t19.piap.pl> (raw)
In-Reply-To: <20220121165707.GA1129091@bhelgaas> (Bjorn Helgaas's message of "Fri, 21 Jan 2022 10:57:07 -0600")
Bjorn Helgaas <helgaas@kernel.org> writes:
> Thanks. e1d3f3268b0e and related patches converted individual files
> ("config", "rom", "vpd", etc) to static attributes, but since the
> problem you're seeing is with a directory, it's likely different.
>
> I opened this bugzilla report to try to keep this from getting lost:
> https://bugzilla.kernel.org/show_bug.cgi?id=215515
Ok, thanks.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2022-01-31 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 8:18 PCI: Race condition in pci_create_sysfs_dev_files (can't boot) Krzysztof Hałasa
2021-07-30 9:49 ` Pali Rohár
2022-01-20 23:00 ` Bjorn Helgaas
2022-01-21 7:14 ` Krzysztof Hałasa
2022-01-21 16:57 ` Bjorn Helgaas
2022-01-31 11:56 ` Krzysztof Hałasa [this message]
2022-02-08 23:40 ` Bjorn Helgaas
2022-02-11 12:31 ` Krzysztof Hałasa
2022-02-15 6:35 ` Krzysztof Hałasa
2022-04-01 13:50 ` Koen Vandeputte
2022-04-06 14:08 ` Koen Vandeputte
2022-04-13 12:52 ` Koen Vandeputte
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=m38ruwxgnx.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@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.