Fwd: XFS security fix never sent to -stable?

[Luis Henriques]

On Sun, Dec 08, 2013 at 10:05:30AM -0700, Tim Gardner wrote:
> In case y'all missed this. Looks like Kees did not Cc stable.
> 

Thanks Tim, I'll queue it for the 3.11 kernel.

Cheers,
--
Luis


> 
> -------- Original Message -------- Subject: XFS security fix never
> sent to -stable?  Date: Thu, 5 Dec 2013 16:35:50 -0800 From: Kees
> Cook <keescook at google.com> To: Dwight Engen
> <dwight.engen at oracle.com> CC: LKML <linux-kernel at vger.kernel.org>,
> Brian Foster <bfoster at redhat.com>, Dave Chinner
> <dchinner at redhat.com>, Gao feng <gaofeng at cn.fujitsu.com>, Ben Myers
> <bpm at sgi.com>, Greg KH <gregkh at linuxfoundation.org>
> 
> Hi,
> 
> It looks like 8c567a7fab6e086a0284eee2db82348521e7120c ("xfs: add
> capability check to free eofblocks ioctl") is a security fix that was
> never sent to -stable? From what I can see, it was introduced in 3.8
> by 8ca149de80478441352a8622ea15fae7de703ced ("xfs: add
> XFS_IOC_FREE_EOFBLOCKS ioctl").
> 
> I don't see this in the 3.8.y tree. Should it be added there and newer?
> 
> Thanks,
> 
> -Kees
> 
> -- 
> Kees Cook
> Chrome OS Security
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
>