From: Borislav Petkov <bp@alien8.de>
To: Kees Cook <keescook@chromium.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Jessica Yu <jeyu@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Slaby <jslaby@suse.cz>, Jiri Olsa <jolsa@kernel.org>,
Michal Marek <mmarek@suse.cz>, Jiri Kosina <jkosina@suse.cz>,
Takashi Iwai <tiwai@suse.de>, Petr Mladek <pmladek@suse.com>,
Jeff Mahoney <jeffm@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86-ml <x86@kernel.org>
Subject: Re: [RFC PATCH] kernel/panic: Add TAINT_AUX
Date: Mon, 11 Sep 2017 18:31:02 +0200 [thread overview]
Message-ID: <20170911163102.fgebdut27iorgrgu@pd.tnic> (raw)
In-Reply-To: <CAGXu5jJx3AF7XB1hb+8vPCHJReYeRsumdFSUCLLOmiR3LrG4Ow@mail.gmail.com>
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.
prev parent reply other threads:[~2017-09-11 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 13:45 Borislav Petkov
2017-09-11 16:19 ` Kees Cook
2017-09-11 16:31 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170911163102.fgebdut27iorgrgu@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=jeffm@suse.com \
--cc=jeyu@redhat.com \
--cc=jkosina@suse.cz \
--cc=jolsa@kernel.org \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®