[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150815002354.7fb2f21e.akpm@linux-foundation.org>
Date: Sat, 15 Aug 2015 00:23:54 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, Michal Marek <mmarek@...e.cz>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>,
Pedro Alves <palves@...hat.com>,
Namhyung Kim <namhyung@...il.com>,
Bernd Petrovitsch <bernd@...rovitsch.priv.at>,
"Chris J Arges" <chris.j.arges@...onical.com>,
live-patching@...r.kernel.org
Subject: Re: [PATCH v10 03/20] x86/stackvalidate: Compile-time stack
validation
On Thu, 13 Aug 2015 22:10:24 -0500 Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> This adds a CONFIG_STACK_VALIDATION option which enables a host tool
> named stackvalidate which runs at compile time.
It would be useful to
- show example output for a typical error site
- describe the consequences of that error (ie: why should we fix
these things?)
- describe what needs to be done to repair these sites.
IOW, what do we gain from merging all this stuff?
--
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