[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170911163102.fgebdut27iorgrgu@pd.tnic>
Date: Mon, 11 Sep 2017 18:31:02 +0200
From: Borislav Petkov <bp@...en8.de>
To: Kees Cook <keescook@...omium.org>
Cc: lkml <linux-kernel@...r.kernel.org>, Jessica Yu <jeyu@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Jiri Slaby <jslaby@...e.cz>, Jiri Olsa <jolsa@...nel.org>,
Michal Marek <mmarek@...e.cz>, Jiri Kosina <jkosina@...e.cz>,
Takashi Iwai <tiwai@...e.de>, Petr Mladek <pmladek@...e.com>,
Jeff Mahoney <jeffm@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
x86-ml <x86@...nel.org>
Subject: Re: [RFC PATCH] kernel/panic: Add TAINT_AUX
On Mon, Sep 11, 2017 at 09:19:16AM -0700, Kees Cook wrote:
> If I were an end-user looking at my kernel trace that had an "X" flag,
> how would I go look up what it actually means? Is "git grep TAINT_AUX"
> going to sufficiently answer that question?
Just like with the other taint letters. I look it up by looking at the
comment over print_tainted(). Unless it is P or M - those I know :-)
> How does SUSE use it currently?
We will use it to mark modules for which we don't provide support. I.e.,
a really eXternal module :-)
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists