On Mon, 2013-02-25 at 11:46 -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 22, 2013 at 09:07:42AM -0800, Greg KH wrote:
> > On Fri, Feb 22, 2013 at 11:57:04AM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Fri, Feb 22, 2013 at 08:19:30AM -0800, Greg KH wrote:
> > > > On Fri, Feb 22, 2013 at 10:46:45AM -0500, Konrad Rzeszutek Wilk wrote:
> > > > > Hey Greg,
> > > > >
> > > > > Please put git commit 51ac8893a7a51b196501164e645583bf78138699
> > > > > commit 51ac8893a7a51b196501164e645583bf78138699
> > > > > Author: Jan Beulich <jbeulich@xxxxxxxx>
> > > > > Date: Wed Feb 6 10:30:38 2013 -0500
> > > > >
> > > > > xen-pciback: rate limit error messages from xen_pcibk_enable_msi{,x}()
> > > > >
> > > > > on the stable tree please. It is an security errata fix and should
> > > > > have had the CC: stable@xxxxxxxxxxxxxxx but did not.
> > > >
> > > > Thanks, what stable kernel releases should it be queued up for?
> > >
> > > 3.4 and later please.
> >
> > On Fri, Feb 22, 2013 at 04:45:55PM +0000, Jan Beulich wrote:
> > > Anyone from 3.1 onwards that is still being maintained.
> >
> > Hm, who should I believe here... :)
>
> Just in case my previous email crossed paths or got deleted.
> >
> > It doesn't matter for me, but for the 3.2 tree, it does.
>
> 3.1 and later please.
Queued up for 3.2.
I had to add '#include <linux/ratelimit.h>' in
drivers/xen/xen-pciback/xen-pciback.c, as printk_ratelimited() uses
DEFINE_RATELIMIT_STATE() which is defined in <linux/ratelimit.h>. (In
mainline this is inclued in <linux/device.h>, but really it ought to be
included in <linux/kernel.h> as well.)
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
Attachment:
signature.asc
Description: This is a digitally signed message part