From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752116AbdIKQbG (ORCPT ); Mon, 11 Sep 2017 12:31:06 -0400 Received: from mail.skyhub.de ([5.9.137.197]:59414 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751422AbdIKQbF (ORCPT ); Mon, 11 Sep 2017 12:31:05 -0400 Date: Mon, 11 Sep 2017 18:31:02 +0200 From: Borislav Petkov To: Kees Cook Cc: lkml , Jessica Yu , Peter Zijlstra , Jiri Slaby , Jiri Olsa , Michal Marek , Jiri Kosina , Takashi Iwai , Petr Mladek , Jeff Mahoney , Andrew Morton , Linus Torvalds , x86-ml Subject: Re: [RFC PATCH] kernel/panic: Add TAINT_AUX Message-ID: <20170911163102.fgebdut27iorgrgu@pd.tnic> References: <20170911134533.dp5mtyku5bongx4c@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.