From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Ravi Kumar Bandi <ravib@amazon.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/sysfs: Check IORESOURCE_DISABLED in resource mmap handler
Date: Tue, 12 May 2026 18:26:14 +0900 [thread overview]
Message-ID: <20260512091848.GA1539393@rocinante> (raw)
In-Reply-To: <20260512084315.32564-1-ravib@amazon.com>
Hello,
> pci_mmap_resource() does not check IORESOURCE_DISABLED before mapping
> a PCI BAR resource into userspace. This allows new mmaps to succeed
> even after a device has been marked disabled or soft-unplugged by the
> driver to prevent further access.
Which driver disables resources? Would this be some Amazon-specific thing
you are trying to fix? Or are you just manually disabling a given device
using sysfs, or something like this?
For "soft-unplugged" device we have pci_dev_set_disconnected(), but this
does not check current flags set.
What is your use case here?
> Add the check to return -ENODEV when the resource is disabled, blocking
> new userspace mmaps of BAR resources after device removal.
>
> Tested by marking the PCI BAR resource as disabled and verifying that
> a subsequent mmap attempt fails with -ENODEV.
Can you explain how did you do this?
> @@ -1089,6 +1089,9 @@ static int pci_mmap_resource(struct kobject *kobj, const struct bin_attribute *a
> if (ret)
> return ret;
>
> + if (res->flags & IORESOURCE_DISABLED)
> + return -ENODEV;
> +
This probably would be better if it checked IORESOURCE_DISABLED and
IORESOURCE_UNSET, but then probably using resource_assigned() would
be even better.
Thank you!
Krzysztof
next prev parent reply other threads:[~2026-05-12 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 8:43 [PATCH] PCI/sysfs: Check IORESOURCE_DISABLED in resource mmap handler Ravi Kumar Bandi
2026-05-12 9:26 ` Krzysztof Wilczyński [this message]
2026-05-12 9:43 ` Ilpo Järvinen
2026-05-12 9:54 ` Krzysztof Wilczyński
2026-05-13 4:04 ` Ravi Kumar Bandi
2026-05-13 5:07 ` Krzysztof Wilczyński
2026-05-13 6:48 ` Ravi Kumar Bandi
2026-05-13 4:13 ` [PATCH v2] PCI/sysfs: Check if device disabled " Ravi Kumar Bandi
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=20260512091848.GA1539393@rocinante \
--to=kwilczynski@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ravib@amazon.com \
/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