From: Jiri Slaby <jirislaby@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: regd: sleeping in atomic
Date: Tue, 16 Mar 2010 14:26:01 +0100 [thread overview]
Message-ID: <4B9F86E9.2030702@gmail.com> (raw)
Hi,
Stanse found an atomic error in reg_copy_regd:
static int reg_copy_regd(const struct ieee80211_regdomain **dst_regd,
const struct ieee80211_regdomain *src_regd)
{
struct ieee80211_regdomain *regd;
int size_of_regd = 0;
unsigned int i;
size_of_regd = sizeof(struct ieee80211_regdomain) +
((src_regd->n_reg_rules + 1) * sizeof(struct
ieee80211_reg_rule));
regd = kzalloc(size_of_regd, GFP_KERNEL); <---- here
Called from:
static void reg_regdb_search(struct work_struct *work)
{
spin_lock(®_regdb_search_lock);
while (!list_empty(®_regdb_search_list)) {
...
for (i=0; i<reg_regdb_size; i++) {
curdom = reg_regdb[i];
if (!memcmp(request->alpha2, curdom->alpha2, 2)) {
r = reg_copy_regd(®dom, curdom);
...
spin_unlock(®_regdb_search_lock);
}
Whole error temporarily available at:
http://decibel.fi.muni.cz/~xslaby/stanse/error.cgi?db=34-rc&id=578
It is introduced by 3b377ea9d4efc94dc52fe41b4dfdb463635ab298.
Do you plan to extend it somehow or may the spinlock be converted to
mutex? If not how much may size_of_regd be -- can we safely switch to
GFP_ATOMIC?
--
js
next reply other threads:[~2010-03-16 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 13:26 Jiri Slaby [this message]
2010-03-16 16:18 ` regd: sleeping in atomic Luis R. Rodriguez
2010-03-16 18:42 ` Jiri Slaby
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=4B9F86E9.2030702@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.