From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: To: Dan Carpenter From: "Martin K. Petersen" References: <20140819144839.GA1270@thunk.org> <20140819145547.GB18536@roeck-us.net> <20140819152350.GE11085@thunk.org> <20140819154029.GE5423@mwanda> <20140819154738.GB16948@roeck-us.net> <20140819160917.GF5423@mwanda> Date: Tue, 19 Aug 2014 12:34:58 -0400 In-Reply-To: <20140819160917.GF5423@mwanda> (Dan Carpenter's message of "Tue, 19 Aug 2014 19:09:17 +0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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: , >>>>> "Dan" == Dan Carpenter writes: Dan> If you rmmod a module it probably means that your code was buggy Dan> before you started the rmmod. We already taint the kernel when the Dan> kernel oopses. It's the same thing. Buggy does not imply that the rest of the kernel is left in a mangled state. Also, I load and unload device driver modules many, many times per day. A significant win on large systems that take half an hour to boot. -- Martin K. Petersen Oracle Linux Engineering