From: Jon Grimm <jgrimm2@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Luc Van Oostenryck <luc.vanoostenryck@easynet.be>,
Thomas Molina <tmolina@cox.net>,
lksctp-developers@lists.sourceforge.net,
Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Lksctp-developers] Re: (more) Sleeping function called from illegal context...
Date: Mon, 30 Sep 2002 07:50:19 -0500 [thread overview]
Message-ID: <3D98488B.DF793D13@us.ibm.com> (raw)
In-Reply-To: 3D950590.1F9FBDC6@digeo.com
Thanks. We'll fix it up.
Best Regards,
Jon Grimm
Andrew Morton wrote:
>
>
> sctp_v4_get_local_addr_list():
>
> /* XXX BUG: sleeping allocation with lock held -DaveM */
> addr = t_new(struct sockaddr_storage_list, GFP_KERNEL);
>
> Is true. We're holding dev_base_lock, inetdev_lock and in_dev->lock
> here.
>
next prev parent reply other threads:[~2002-09-30 13:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 23:30 Sleeping function called from illegal context Greg KH
2002-09-27 23:50 ` Andrew Morton
2002-09-28 0:43 ` (more) " Luc Van Oostenryck
2002-09-28 1:22 ` Andrew Morton
2002-09-28 0:44 ` Luc Van Oostenryck
2002-09-28 1:24 ` Andrew Morton
2002-09-28 2:15 ` Greg KH
2002-09-28 0:44 ` Luc Van Oostenryck
2002-09-28 1:27 ` Andrew Morton
2002-09-30 12:50 ` Jon Grimm [this message]
2002-09-30 13:34 ` [Lksctp-developers] " Jon Grimm
2002-09-28 2:04 ` Andre Hedrick
2002-09-28 3:06 ` Robert Love
2002-09-28 3:21 ` Andre Hedrick
2002-09-28 3:29 ` Robert Love
2002-09-28 10:06 ` Alan Cox
2002-09-28 17:06 ` Robert Love
2002-09-28 0:51 ` Robert Love
2002-09-28 2:16 ` Greg KH
2002-09-28 14:54 ` John Levon
2002-09-28 17:05 ` Andrew Morton
2002-09-28 17:24 ` John Levon
2002-09-28 18:27 ` Robert Love
2002-09-28 18:38 ` John Levon
2002-09-29 0:50 ` William Lee Irwin III
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=3D98488B.DF793D13@us.ibm.com \
--to=jgrimm2@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=luc.vanoostenryck@easynet.be \
--cc=tmolina@cox.net \
/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.