From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933491Ab3LIMPl (ORCPT ); Mon, 9 Dec 2013 07:15:41 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:35198 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932532Ab3LIMPk (ORCPT ); Mon, 9 Dec 2013 07:15:40 -0500 Date: Mon, 9 Dec 2013 12:15:34 +0000 From: Luis Henriques To: Kees Cook Cc: Dwight Engen , LKML , Brian Foster , Dave Chinner , Gao feng , Ben Myers , Greg KH Subject: Re: XFS security fix never sent to -stable? Message-ID: <20131209121534.GE4278@hercules> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 05, 2013 at 04:35:50PM -0800, Kees Cook wrote: > 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, I'm queuing it for the 3.11 kernel. Cheers, -- Luis