From: "Krzysztof Wilczyński" <kw@linux.com>
To: Amey Narkhede <ameynarkhede03@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
alex.williamson@redhat.com, raphael.norwitz@nutanix.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 5/7] PCI/sysfs: Allow userspace to query and set device reset mechanism
Date: Thu, 20 May 2021 18:37:37 +0200 [thread overview]
Message-ID: <20210520163737.GD641812@rocinante.localdomain> (raw)
In-Reply-To: <20210519235426.99728-6-ameynarkhede03@gmail.com>
Hi Amey,
[...]
> + if (sysfs_streq(buf, "")) {
> + pci_warn(pdev, "All device reset methods disabled by user");
> + goto set_reset_methods;
> + }
The sysfs_streq() is nice, indeed.
> + while ((name = strsep((char **)&buf, ",")) != NULL) {
I believe we could make this parsing a little bit more resilient,
especially since we are handling user input and this cannot ever be
really fully trusted, so for example:
while ((name = strsep((char **)&buf, ","))) {
if !(strlen(name)) <--- sysfs_streq() could be used here too.
continue;
name = strim(name); <--- remove leading and trailing whitespaces, if any.
(...)
[...]
> + if (reset_methods[0] &&
> + reset_methods[0] != PCI_RESET_FN_METHODS)
> + pci_warn(pdev, "Device specific reset disabled/de-prioritized by user");
What would be difference between disabling and de-prioritizing, is there
be a way for us to distinguish between the two? I was wondering if we
could, notify the user when the device specific reset is disable or when
it has been de-prioritized?
Krzysztof
next prev parent reply other threads:[~2021-05-20 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 23:54 [PATCH RESEND v2 0/7] Expose and manage PCI device reset Amey Narkhede
2021-05-19 23:54 ` [PATCH RESEND v2 1/7] PCI: merge slot and bus reset implementations Amey Narkhede
2021-05-20 14:54 ` Krzysztof Wilczyński
2021-05-19 23:54 ` [PATCH RESEND v2 2/7] PCI: Add pcie_reset_flr to follow calling convention of other reset methods Amey Narkhede
2021-05-20 15:05 ` Krzysztof Wilczyński
2021-05-24 14:48 ` Amey Narkhede
2021-05-25 15:17 ` Krzysztof Wilczyński
2021-05-25 16:03 ` Amey Narkhede
2021-05-19 23:54 ` [PATCH RESEND v2 3/7] PCI: Add new array for keeping track of ordering of " Amey Narkhede
2021-05-20 15:26 ` Krzysztof Wilczyński
2021-05-19 23:54 ` [PATCH RESEND v2 4/7] PCI: Remove reset_fn field from pci_dev Amey Narkhede
2021-05-19 23:54 ` [PATCH RESEND v2 5/7] PCI/sysfs: Allow userspace to query and set device reset mechanism Amey Narkhede
2021-05-20 16:37 ` Krzysztof Wilczyński [this message]
2021-05-19 23:54 ` [PATCH RESEND v2 6/7] PCI: Add support for a function level reset based on _RST method Amey Narkhede
2021-05-19 23:54 ` [PATCH RESEND v2 7/7] PCI: Enable NO_BUS_RESET quirk for Nvidia GPUs Amey Narkhede
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=20210520163737.GD641812@rocinante.localdomain \
--to=kw@linux.com \
--cc=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=raphael.norwitz@nutanix.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