From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 19 Aug 2014 19:09:17 +0300 From: Dan Carpenter To: Guenter Roeck Message-ID: <20140819160917.GF5423@mwanda> References: <20140819144839.GA1270@thunk.org> <20140819145547.GB18536@roeck-us.net> <20140819152350.GE11085@thunk.org> <20140819154029.GE5423@mwanda> <20140819154738.GB16948@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140819154738.GB16948@roeck-us.net> Cc: ksummit-discuss@lists.linux-foundation.org Subject: Re: [Ksummit-discuss] No more module removal -- Unconference track List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Aug 19, 2014 at 08:47:38AM -0700, Guenter Roeck wrote: > On Tue, Aug 19, 2014 at 06:40:29PM +0300, Dan Carpenter wrote: > > Why can't we just taint the kernel on module removal? > > > Why not just fix its bugs ? > > If you want to taint the kernel on module removal because it is known that many > drivers have bugs in their removal code, you should taint the kernel if any code > is used which is known to have a bug. Or, in other words, just taint the kernel, > period. If you rmmod a module it probably means that your code was buggy before you started the rmmod. We already taint the kernel when the kernel oopses. It's the same thing. regards, dan carpenter