linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sasha Levin <sasha.levin@oracle.com>,
	Prarit Bhargava <prarit@redhat.com>
Subject: [GIT PULL] PCI fixes for v4.3
Date: Thu, 29 Oct 2015 18:54:44 -0500	[thread overview]
Message-ID: <20151029235444.GC11994@localhost> (raw)

Hi Linus,

Sorry for this last-minute update; it's been in -next for quite a while,
but I forgot about it until I started getting ready for the merge window.

It's small and fixes a way a user could cause a panic via sysfs, so I think
it's worth getting it in v4.3.

Bjorn


The following changes since commit de24c18c0faca5ebd618e1cb87f5489745e40475:

  PCI: rcar: Add R8A7794 support (2015-09-24 17:06:32 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.3-fixes-2

for you to fetch changes up to 1266963170f576d4d08e6310b6963e26d3ff9d1e:

  PCI: Prevent out of bounds access in numa_node override (2015-10-07 11:03:28 -0500)

----------------------------------------------------------------
PCI update for v4.3:

  NUMA
    - Prevent out of bounds access in sysfs numa_node override (Sasha Levin)

----------------------------------------------------------------
Sasha Levin (1):
      PCI: Prevent out of bounds access in numa_node override

 drivers/pci/pci-sysfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2015-10-29 23:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 23:54 Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-25 13:29 [GIT PULL] PCI fixes for v4.3 Bjorn Helgaas

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=20151029235444.GC11994@localhost \
    --to=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=sasha.levin@oracle.com \
    --cc=torvalds@linux-foundation.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 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).