From: Samuel Jean <sj-netfilter@cookinglinux.org>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: [PATCH 2/2] ipt_hashlimit.c: sleeping function called from invalid context
Date: Wed, 26 Jan 2005 22:51:51 -0500 [thread overview]
Message-ID: <41F86557.2000208@cookinglinux.org> (raw)
Name: sleeping function called from invalid context
Status: Tested under Linux 2.6.10
Signed-off-by: Samuel Jean <sjean@cookinglinux.org>
When we cat our proc entries, we get:
Jan 26 22:07:33 Workstation kernel: Debug: sleeping function called from invalid context at
mm/slab.c:2055
Jan 26 22:07:33 Workstation kernel: in_atomic():1, irqs_disabled():0
Jan 26 22:07:33 Workstation kernel: [<c0116f80>] __might_sleep+0xb0/0xe0
Jan 26 22:07:33 Workstation kernel: [<c013f3ec>] kmem_cache_alloc+0x6c/0x70
Jan 26 22:07:33 Workstation kernel: [<e0a84b31>] dl_seq_start+0x61/0x80 [ipt_hashlimit]
Jan 26 22:07:33 Workstation kernel: [<c01752bf>] seq_read+0xbf/0x2b0
Jan 26 22:07:33 Workstation kernel: [<c0154618>] vfs_read+0xb8/0x130
Jan 26 22:07:33 Workstation kernel: [<c0154901>] sys_read+0x51/0x80
Jan 26 22:07:33 Workstation kernel: [<c01031bf>] syscall_call+0x7/0xb
This incremental patch to the previous fixes it by disallowing kmalloc to sleep.
--- net/ipv4/netfilter/ipt_hashlimit.c.orig 2005-01-26 22:35:43.000000000 -0500
+++ net/ipv4/netfilter/ipt_hashlimit.c 2005-01-26 22:36:14.000000000 -0500
@@ -570,7 +570,7 @@ static void *dl_seq_start(struct seq_fil
if (*pos >= htable->cfg.size)
return NULL;
- bucket = kmalloc(sizeof(unsigned int), GFP_KERNEL);
+ bucket = kmalloc(sizeof(unsigned int), GFP_ATOMIC);
if (!bucket)
return ERR_PTR(-ENOMEM);
next reply other threads:[~2005-01-27 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 3:51 Samuel Jean [this message]
2005-02-01 15:07 ` [PATCH 2/2] ipt_hashlimit.c: sleeping function called from invalid context Samuel Jean
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=41F86557.2000208@cookinglinux.org \
--to=sj-netfilter@cookinglinux.org \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
/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.