[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090103224408.GC17047@elte.hu>
Date: Sat, 3 Jan 2009 23:44:08 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [git pull] stackprotector re-enabling patches
* Arjan van de Ven <arjan@...radead.org> wrote:
> On Sat, 3 Jan 2009 13:55:13 -0800
> Arjan van de Ven <arjan@...radead.org> wrote:
>
> > On Sat, 3 Jan 2009 22:43:53 +0100
> > Ingo Molnar <mingo@...e.hu> wrote:
> > >
> > > diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
> > > index 10d6cc3..28f1114 100644
> > > --- a/arch/x86/Kconfig.debug
> > > +++ b/arch/x86/Kconfig.debug
> > > @@ -117,6 +117,7 @@ config DEBUG_RODATA
> > > config DEBUG_RODATA_TEST
> > > bool "Testcase for the DEBUG_RODATA feature"
> > > depends on DEBUG_RODATA
> > > + default y
> > > help
> > > This option enables a testcase for the DEBUG_RODATA
> > > feature as well as for the change_page_attr()
> >
> > I think this chunk isn't meant to be there...
>
> actually never mind.
> it does make sense in general (in fact, I'd be tempted to remove the
> KConfig for this one and just always do the check)
yes. The reason why this change went into the stackprotector tree was
because it was the same pattern: security feature breaking because it
didnt have efficient self-tests - while attackers obviously never notified
us that it's broken.
DEBUG_RODATA had similar bugs: it didnt work correctly in some cases and
nothing really tested that so we had long latency of bugs. So i turned on
that self-test too. [and that did catch some bugs, which you fixed, many
moons ago ;-) ]
Ingo
--
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