From: Jeff Garzik <jgarzik@pobox.com>
To: Ben Collins <bcollins@debian.org>
Cc: Philippe Gramoull? <philippe.gramoulle@mmania.com>,
linux-kernel@vger.kernel.org,
Linux IEEE 1394 Devel Mailing List
<linux1394-devel@lists.sourceforge.net>
Subject: Re: 2.6.0-test1-mm1: bad: scheduling while atomic! after removing ohci1394 module
Date: Wed, 16 Jul 2003 12:45:06 -0400 [thread overview]
Message-ID: <20030716164506.GD5628@gtf.org> (raw)
In-Reply-To: <20030716163648.GO685@phunnypharm.org>
On Wed, Jul 16, 2003 at 12:36:48PM -0400, Ben Collins wrote:
> So is kill_proc() bad while atomic, e.g. when a module is being removed?
> I'll look into it.
hmmm, that's a big strange. During ->remove and module unload, you can
schedule and sleep.
Jeff
next prev parent reply other threads:[~2003-07-16 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 16:08 2.6.0-test1-mm1: bad: scheduling while atomic! after removing ohci1394 module Philippe Gramoullé
2003-07-16 16:36 ` Ben Collins
2003-07-16 16:45 ` Jeff Garzik [this message]
2003-07-16 16:53 ` Ben Collins
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=20030716164506.GD5628@gtf.org \
--to=jgarzik@pobox.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=philippe.gramoulle@mmania.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.