[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a781481a0706220519y1d6c8044mac19d4da9dfc3df2@mail.gmail.com>
Date: Fri, 22 Jun 2007 17:49:41 +0530
From: "Satyam Sharma" <satyam.sharma@...il.com>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: "Carsten Otte" <cotte@...ibm.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Yan Zheng" <yanzheng@...n.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [BUG?]Set XIP mount option on ext2 bypass check.
Hi,
On 6/22/07, Arnd Bergmann <arnd@...db.de> wrote:
> On Thursday 21 June 2007, Carsten Otte wrote:
> >
> > This is an updated version of my bugfix patch. Yan Zheng pointed out,
> > that ext2_remount lacks checking if -o xip should be enabled or not.
> > This patch checks for presence of direct_access on the backing block
> > device and if the blocksize meets the requirements.
> > Andrew, please consider adding this patch to -mm.
> >
> > Signed-off-by: Carsten Otte <cotte@...ibm.com>
>
> It looks to me like a local denial of service attack in case of
> user-mountable ext2 file systems in /etc/fstab.
>
> Shouldn't that make it go into 2.6.22?
I agree. I would go on to suggest that all trivially-triggered oopsen /
panics from userspace (even if they require privileges, such as the
cat /dev/snapshot == oops issue posted last week) in fact ought to
be CVE's, and the corresponding fixes for such issues be considered
as candidates for -stable, if applicable to the current stable kernel.
Satyam
-
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