linux-kernel - Re: [GIT PULL] vfio fix for 3.9-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 09 Apr 2013 13:43:05 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	kvm <kvm@...r.kernel.org>,
	Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [GIT PULL] vfio fix for 3.9-rc7

On Tue, 2013-04-09 at 21:40 +0200, richard -rw- weinberger wrote:
> On Tue, Apr 9, 2013 at 9:05 PM, Alex Williamson
> <alex.williamson@...hat.com> wrote:
> > Hi Linus,
> >
> > Here's one small fix for vfio that I'd like to get in for 3.9;
> > tightening the range checking around a vfio ioctl.  Thanks!
> >
> > Alex
> >
> > The following changes since commit 25e9789ddd9d14a8971f4a421d04f282719ab733:
> >
> >   vfio: include <linux/slab.h> for kmalloc (2013-03-15 12:58:20 -0600)
> >
> > are available in the git repository at:
> >
> >   git://github.com/awilliam/linux-vfio.git tags/vfio-v3.9-rc7
> >
> > for you to fetch changes up to 904c680c7bf016a8619a045850937427f8d7368c:
> >
> >   vfio-pci: Fix possible integer overflow (2013-03-26 11:33:16 -0600)
> 
> Is this commit queued for -stable?
> I don't see a stable tag in the commit message.

No, I forgot to add it.  I'll take the long way around and send it to
stable once it's applied.  Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/