From: Alexey Dobriyan <adobriyan@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Nathan Zimmer <nzimmer@sgi.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] fs/proc: Move kfree outside pde_unload_lock
Date: Wed, 29 Aug 2012 11:32:26 +0300 [thread overview]
Message-ID: <20120829083226.GA4511@p183.telecom.by> (raw)
In-Reply-To: <1346213517.2522.2.camel@edumazet-glaptop>
On Tue, Aug 28, 2012 at 09:11:57PM -0700, Eric Dumazet wrote:
> On Tue, 2012-08-28 at 23:38 +0300, Alexey Dobriyan wrote:
>
> > Nothing can stop RCU!
> >
> > After running "modprobe;rmmod" in a loop and "cat" in another loop for a while
> > rmmod got stuck in D-state inside remove_proc_entry() with trace amounts of CPU time
> > being consumed.
> >
> > It didn't oopsed, though.
>
> Thanks !
>
> I'll polish this patch once LKS/LPC is over...
>
> What particular module and/or proc file did you use for your tests ?
Just dummy one.
#include <linux/init.h>
#include <linux/proc_fs.h>
#include <linux/seq_file.h>
static int foo_proc_show(struct seq_file *m, void *v)
{
seq_puts(m, "foo\n");
return 0;
}
static int foo_proc_open(struct inode *inode, struct file *file)
{
return single_open(file, foo_proc_show, NULL);
}
static const struct file_operations foo_proc_ops = {
.open = foo_proc_open,
.read = seq_read,
.llseek = seq_lseek,
.release = single_release,
};
static int __init foo_module_init(void)
{
proc_create("foo", 0, NULL, &foo_proc_ops);
return 0;
}
static void __exit foo_module_exit(void)
{
remove_proc_entry("foo", NULL);
}
module_init(foo_module_init);
module_exit(foo_module_exit);
next prev parent reply other threads:[~2012-08-29 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 16:38 [PATCH] fs/proc: Move kfree outside pde_unload_lock Nathan Zimmer
2012-08-22 16:38 ` [PATCH] fs/prof: Update comment on pde_unload_lock Nathan Zimmer
2012-08-22 18:28 ` [PATCH] fs/proc: Move kfree outside pde_unload_lock Eric Dumazet
2012-08-22 21:42 ` Eric Dumazet
2012-08-23 17:54 ` Nathan Zimmer
2012-08-24 14:48 ` Nathan Zimmer
2012-08-24 14:58 ` Eric Dumazet
2012-08-24 16:45 ` Nathan Zimmer
2012-08-24 21:43 ` Nathan Zimmer
2012-08-28 20:38 ` Alexey Dobriyan
2012-08-29 4:11 ` Eric Dumazet
2012-08-29 8:32 ` Alexey Dobriyan [this message]
2012-08-29 13:50 ` Alexey Dobriyan
2012-08-29 14:24 ` Eric Dumazet
2012-09-17 15:57 ` Nathan Zimmer
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=20120829083226.GA4511@p183.telecom.by \
--to=adobriyan@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nzimmer@sgi.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).