Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753045AbdHNQuV (ORCPT ); Mon, 14 Aug 2017 12:50:21 -0400 Received: from mail-it0-f48.google.com ([209.85.214.48]:37221 "EHLO mail-it0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752203AbdHNQuT (ORCPT ); Mon, 14 Aug 2017 12:50:19 -0400 MIME-Version: 1.0 In-Reply-To: <20170810204328.kk4lbj4hvednmofw@redbean> References: <20170804180751.14896-1-mjg59@google.com> <20170810204328.kk4lbj4hvednmofw@redbean> From: Matthew Garrett Date: Mon, 14 Aug 2017 12:50:17 -0400 Message-ID: Subject: Re: Allow automatic kernel taint on unsigned module load to be disabled To: Jessica Yu Cc: linux-kernel@vger.kernel.org, Rusty Russell Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 495 Lines: 10 On Thu, Aug 10, 2017 at 4:43 PM, Jessica Yu wrote: > I think I'm missing some context here. Could you provide some more > background and help me understand why we want to go into all this > trouble just to avoid a taint? Was there a recent bug report, mailing > list discussion, etc. that spurred you to write this patch? I'm not > understanding why this particular taint is undesirable. Hi Jessica, Does the version in https://lkml.org/lkml/2017/8/7/764 make this clearer?