From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 19 Aug 2014 17:54:26 +0200 Message-ID: From: Takashi Iwai To: Theodore Ts'o In-Reply-To: <20140819152350.GE11085@thunk.org> References: <20140819144839.GA1270@thunk.org> <20140819145547.GB18536@roeck-us.net> <20140819152350.GE11085@thunk.org> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII 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: , At Tue, 19 Aug 2014 11:23:50 -0400, Theodore Ts'o wrote: > > On Tue, Aug 19, 2014 at 07:55:47AM -0700, Guenter Roeck wrote: > > On Tue, Aug 19, 2014 at 10:48:39AM -0400, Theodore Ts'o wrote: > > > This has been scheduled at 2pm at the request of Rusty. (Reminder: if > > > you're going to propose a topic, please send e-mail to start a thread > > > on ksummit-discuss). > > > > > Do we have a context ? I am using insert/remove module a lot during testing, > > and would hate to see it go. It also permits module updates without having to > > reboot the kernel. There must be lots of other reasons to support module > > removal. So I would really dislike if it was no longer available, and I don't > > really see the point. > > Rusty has been trying to nuke module removal for years. > > Unfortunately, it's been incredibly useful for many reasons. > > In addition to the reasons you've suggested, it's the only way that I > can reset a malfunctioning sound driver without rebooting, and I'd > hate to have to regress to windows style "reboot to fix the problem". Oh, please report such a problem. Or wait, maybe we shouldn't debug it for keeping one more vote for the election "save module removal" :) Takashi