From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: regd: sleeping in atomic
Date: Tue, 16 Mar 2010 19:42:38 +0100 [thread overview]
Message-ID: <4B9FD11E.5050108@gmail.com> (raw)
In-Reply-To: <43e72e891003160918x3b7e3c9asf4fc8a9db35ccd8a@mail.gmail.com>
On 03/16/2010 05:18 PM, Luis R. Rodriguez wrote:
> one iteration of call_crda() which happens during module
> initialization and from what I gather I don't think the kernel is
> happy when you mutex_lock on load routines, please correct my foggy
> memory if I am mistaken.
No, using mutex in init/exit module routines is fine. Where do you have
the information from? There might be problems only with request_module,
flush_scheduled_work or similar.
next prev parent reply other threads:[~2010-03-16 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 13:26 regd: sleeping in atomic Jiri Slaby
2010-03-16 16:18 ` Luis R. Rodriguez
2010-03-16 18:42 ` Jiri Slaby [this message]
2010-03-16 20:36 ` Luis R. Rodriguez
2010-03-16 19:49 ` [PATCH] wireless: convert reg_regdb_search_lock to mutex John W. Linville
2010-03-16 10:03 ` Senthil Balasubramanian
2010-03-17 0:24 ` John W. Linville
2010-03-16 12:24 ` Senthil Balasubramanian
2010-03-17 2:56 ` John W. Linville
2010-03-17 3:24 ` Johannes Berg
2010-03-17 1:26 ` Senthil Balasubramanian
2010-03-17 12:55 ` John W. Linville
2010-03-17 13:01 ` John W. Linville
2010-03-17 19:33 ` [PATCH v2] " John W. Linville
2010-03-18 20:47 ` [PATCH v3] " John W. Linville
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=4B9FD11E.5050108@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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.