Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264299AbUD0Tns (ORCPT ); Tue, 27 Apr 2004 15:43:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264315AbUD0TmJ (ORCPT ); Tue, 27 Apr 2004 15:42:09 -0400 Received: from piedra.unizar.es ([155.210.11.65]:5510 "EHLO relay.unizar.es") by vger.kernel.org with ESMTP id S264310AbUD0Tl5 (ORCPT ); Tue, 27 Apr 2004 15:41:57 -0400 From: "Jorge Bernal (Koke)" Reply-To: koke@sindominio.net To: linux-kernel@vger.kernel.org Subject: Re: [PATCH] Blacklist binary-only modules lying about their license Date: Tue, 27 Apr 2004 21:41:51 +0200 User-Agent: KMail/1.6.1 Cc: Grzegorz Kulewski , Valdis.Kletnieks@vt.edu References: <20040427165819.GA23961@valve.mbsi.ca> <200404272103.21925.koke_lkml@amedias.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404272141.51222.koke_lkml@amedias.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 877 Lines: 26 On Martes, 27 de Abril de 2004 21:16, Grzegorz Kulewski wrote: > > I think that /proc/tainted would be better than spamming logs after each > load of tainted module... > But probably modules should not be removed from /proc/tainted on unloading > (to prevent from "un-tainting" the kernel by "clever" users). > 2 ideas: Printing if the tainted module is loaded or unloaded and/or using the /proc/tainted interface to enable/disable loading of tainted modules. So that are 2 different things: a) how do we handle the tainted mods notifications and b) if we let the user decide if he/she wants tainted modules to be "blocked" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/