From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Bates <sbates@raithlin.com>,
Andrew Maier <andrew.maier@eideticom.com>
Subject: Re: [PATCH] PCI: Fix issue with "pci=disable_acs_redir" parameter being ignored
Date: Fri, 5 Apr 2019 16:39:40 -0500 [thread overview]
Message-ID: <20190405213939.GC159318@google.com> (raw)
In-Reply-To: <20190401193302.12813-1-logang@deltatee.com>
On Mon, Apr 01, 2019 at 01:33:02PM -0600, Logan Gunthorpe wrote:
> In most cases, kmalloc will not be available early in boot when
> pci_setup() is called. Thus, the kstrdup call that was added to fix the
> __initdata bug with the disable_acs_redir parameter usually returns
> NULL. Thus the parameter is discarded and it does not take into effect.
>
> To fix this we have to do what we originally did with the
> resource_alignment parameter: allocate a static buffer and copy the
> string from the command line to it.
>
> Fixes: d2fd6e81912a ("PCI: Fix __initdata issue with "pci=disable_acs_redir" parameter")
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> Tested-by: Andrew Maier <andrew.maier@eideticom.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> ---
>
> Sorry, it seems I didn't test the previous patch in this area properly
> and I actually made disable_acs_redir ineffective in most cases.
>
> This change should fix it and I got a colleague to test it fully
> on his system as well.
>
> drivers/pci/pci.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 7c1b362f599a..537395dfd0df 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -3125,7 +3125,17 @@ void pci_request_acs(void)
> pci_acs_enable = 1;
> }
>
> -static const char *disable_acs_redir_param;
> +static char disable_acs_redir_param[COMMAND_LINE_SIZE];
I certainly acknowledge the problem, but I'm a little hesitant to add
a static buffer of 256-4096 bytes (2048 on x86, arm64, powerpc, sparc)
for a relatively low-usage situation. The memory usage doesn't seem
in proportion to the value-add.
Ugh, and we allocate another similar buffer for
resource_alignment_param[], which I would guess is also rarely used.
Since disable_acs_redir_param[] and resource_alignment_param[] are
both read-only and big enough to hold the entire command line, we
should be able to share a single buffer between them if we made the
parsers a little smarter. In fact, I bet there's already a static
copy lying around somewhere for /proc/cmdline.
> +static void pci_set_disable_acs_redir_param(const char *param)
> +{
> + if (strlen(param) >= sizeof(disable_acs_redir_param)) {
> + pr_err("PCI: disable_acs_redir parameter is too long and has been ignored!\n");
> + return;
> + }
> +
> + strcpy(disable_acs_redir_param, param);
> +}
>
> /**
> * pci_disable_acs_redir - disable ACS redirect capabilities
> @@ -3140,7 +3150,7 @@ static void pci_disable_acs_redir(struct pci_dev *dev)
> int pos;
> u16 ctrl;
>
> - if (!disable_acs_redir_param)
> + if (!disable_acs_redir_param[0])
> return;
>
> p = disable_acs_redir_param;
> @@ -6262,8 +6272,7 @@ static int __init pci_setup(char *str)
> } else if (!strncmp(str, "pcie_scan_all", 13)) {
> pci_add_flags(PCI_SCAN_ALL_PCIE_DEVS);
> } else if (!strncmp(str, "disable_acs_redir=", 18)) {
> - disable_acs_redir_param =
> - kstrdup(str + 18, GFP_KERNEL);
> + pci_set_disable_acs_redir_param(str + 18);
> } else {
> printk(KERN_ERR "PCI: Unknown option `%s'\n",
> str);
> --
> 2.20.1
next prev parent reply other threads:[~2019-04-05 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 19:33 [PATCH] PCI: Fix issue with "pci=disable_acs_redir" parameter being ignored Logan Gunthorpe
2019-04-05 21:39 ` Bjorn Helgaas [this message]
2019-04-05 22:11 ` Logan Gunthorpe
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=20190405213939.GC159318@google.com \
--to=helgaas@kernel.org \
--cc=andrew.maier@eideticom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.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;
as well as URLs for NNTP newsgroup(s).