[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200901161109.21880.borntraeger@de.ibm.com>
Date: Fri, 16 Jan 2009 11:09:21 +0100
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Heiko Carstens <heiko.carstens@...ibm.com>
Cc: Jiri Slaby <jirislaby@...il.com>, Greg KH <gregkh@...e.de>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
"Theodore Ts'o" <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>,
Michael Krufky <mkrufky@...uxtv.org>,
Chuck Ebbert <cebbert@...hat.com>,
Domenico Andreoli <cavokz@...il.com>, Willy Tarreau <w@....eu>,
Rodrigo Rubira Branco <rbranco@...checkpoint.com>,
Jake Edge <jake@....net>, Eugene Teo <eteo@...hat.com>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
alan@...rguk.ukuu.org.uk, Ralf Baechle <ralf@...ux-mips.org>,
Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [patch 27/85] [PATCH 07/44] [CVE-2009-0029] System call wrapper infrastructure
Am Freitag 16 Januar 2009 schrieb Heiko Carstens:
> > I see two possible quick fixes:
> > -funit-at-a-time will allow these inline constructs (tested with 3.4.6 on
i386
> > with enabled syscall wrappers. x86_64 already sets this flag)
>
> If that helps: care to send a patch that enables this?
> Dependent on CONFIG_HAVE_SYSCALL_WRAPPERS?
I could do that, but...
> That is, if this is really a problem.
..I dont know if this is really a problem. i386 is the only architecture where
I was able to reproduce the inline problem. But i386 does not set
SYSCALL_WRAPPERS so the problem goes away.
I suggest to wait for a patch until we know of an architecture that is
affected (inline problem + HAVE_SYSCALL_WRAPPERS set).
--
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