[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090228095433.6af07a89@infradead.org>
Date: Sat, 28 Feb 2009 09:54:33 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Greg KH <greg@...ah.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Roland McGrath <roland@...hat.com>, linux-mips@...ux-mips.org,
x86@...nel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...abs.org, sparclinux@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org
Subject: Re: [stable] [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole
On Sat, 28 Feb 2009 09:46:01 -0800
Greg KH <greg@...ah.com> wrote:
> On Sat, Feb 28, 2009 at 09:23:36AM -0800, Linus Torvalds wrote:
> > On Fri, 27 Feb 2009, Roland McGrath wrote:
> > > But here is the patch you asked for.
> >
> > Yes, this looks much more straightforward.
> >
> > And I guess the seccomp interaction means that this is potentially
> > a 2.6.29 thing. Not that I know whether anybody actually _uses_
> > seccomp. It does seem to be enabled in at least Fedora kernels, but
> > it might not be used anywhere.
>
> It's enabled in SuSE kernels.
>
but are there users of it?
I thought Andrea stopped the cpushare thing that was the only user of
this....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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