From: Robert Marquardt <marquardt@codemercs.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Tejun Heo <htejun@gmail.com>,
Markus Rechberger <markus.rechberger@amd.com>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?
Date: Mon, 16 Apr 2007 16:51:33 +0200 [thread overview]
Message-ID: <46238D75.4010409@codemercs.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0704161028330.4861-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On the other hand, this proposal involves adding a fair amount of overhead
> (all those .owner fields) for a rather small benefit. And it involves
> modifying a core kernel subsystem (kernel/module.c). All to prevent
> certain unlikely sorts of errors when removing a module -- something which
> Linus has said repeatedly need not be supported terribly well.
>
> So I'm uncertain whether other people will be in favor of all this.
I think Linus is in error here. Either do it right or not at all. I
would say that modules should work *always* and without any conceptual
problem.
next prev parent reply other threads:[~2007-04-16 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:23 How should an exit routine wait for release() callbacks? Alan Stern
2007-04-13 9:03 ` Cornelia Huck
2007-04-13 11:42 ` Markus Rechberger
2007-04-13 13:24 ` Cornelia Huck
2007-04-13 14:15 ` Markus Rechberger
2007-04-13 14:27 ` Cornelia Huck
2007-04-13 15:24 ` Alan Stern
2007-04-16 8:53 ` Cornelia Huck
2007-04-16 14:43 ` Alan Stern
2007-04-16 14:51 ` Robert Marquardt [this message]
2007-04-16 15:05 ` Cornelia Huck
2007-04-16 22:12 ` [linux-usb-devel] " Greg KH
2007-04-17 7:26 ` Cornelia Huck
2007-04-17 15:59 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46238D75.4010409@codemercs.com \
--to=marquardt@codemercs.com \
--cc=cornelia.huck@de.ibm.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=markus.rechberger@amd.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox