From: Prarit Bhargava <prarit@redhat.com>
To: Mathias Krause <minipli@googlemail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PATCH] PCI: Prevent out of bounds access in numa_node override - part 2
Date: Mon, 09 Nov 2015 06:13:18 -0500 [thread overview]
Message-ID: <56407FCE.3070201@redhat.com> (raw)
In-Reply-To: <CA+rthh_7u7B5ftoqwaTKRXxt8vio+BRwCoyJ1mJqW5vBRmhiiA@mail.gmail.com>
On 11/09/2015 01:56 AM, Mathias Krause wrote:
>
>> Can you point to the code that does node_states[pci_dev->numa_node] without
>> doing a bounds check? IMO that's the code that is broken.
>
> It's the node_state() inline for MAX_NUMNODES > 1.
In drivers/pci/pci-sysfs.c: numa_node_store()
if (node >= MAX_NUMNODES || !node_online(node))
needs to be broken out into a range and separate online check.
/* range check */
if (node < NUMA_NO_NODE || node >= MAX_NUMNODES)
return -EINVAL;
/* Is the specific node online? */
if (node != NUMA_NO_NODE && !node_online(node))
return -EINVAL; /* perhaps -ENODEV ? */
which will fix the problem.
P.
>
>>
>> FWIW: I think the idea of your patch is still correct. Checking for -1 to
>> MAX_NUMNODES is not a bad idea.
>
> It is. As it prevents userland from triggering the out of bounds read. ;)
>
>
> Thanks,
> Mathias
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-11-09 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 17:24 [PATCH] PCI: Prevent out of bounds access in numa_node override - part 2 Mathias Krause
2015-11-08 23:28 ` Prarit Bhargava
2015-11-09 6:56 ` Mathias Krause
2015-11-09 11:13 ` Prarit Bhargava [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=56407FCE.3070201@redhat.com \
--to=prarit@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=sasha.levin@oracle.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 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.