[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA4ychvLEi1ZZ6rYy2=5-wZAbQ_a-aoy8=1w3+tr-pt3Fg@mail.gmail.com>
Date: Mon, 9 Dec 2013 08:17:09 -0500
From: Josh Boyer <jwboyer@...oraproject.org>
To: Luis Henriques <luis.henriques@...onical.com>
Cc: Kees Cook <keescook@...gle.com>,
Dwight Engen <dwight.engen@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
Brian Foster <bfoster@...hat.com>,
Dave Chinner <dchinner@...hat.com>,
Gao feng <gaofeng@...fujitsu.com>, Ben Myers <bpm@....com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: XFS security fix never sent to -stable?
On Mon, Dec 9, 2013 at 7:15 AM, Luis Henriques
<luis.henriques@...onical.com> wrote:
> 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.
There's also this one:
http://thread.gmane.org/gmane.comp.file-systems.xfs.general/57654
It fixes CVE-2013-6382
josh
--
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/
Powered by blists - more mailing lists