From: Tejun Heo <tj@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: davem@davemloft.net, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
viro@ZenIV.linux.org.uk, akpm@linux-foundation.org
Subject: [PATCH] fs: run emergency remount on dedicated workqueue
Date: Thu, 27 May 2010 11:57:23 +0200 [thread overview]
Message-ID: <4BFE4203.5010803@kernel.org> (raw)
In-Reply-To: <25328.1274886067@redhat.com>
Commit fa4b9074cd8428958c2adf9dc0c831f46e27c193 made s_umount depend
on keventd; however, emergency remount schedules works to keventd
which grabs s_umount creating a circular dependency. Run emergency
remount on a separate workqueue to break it.
Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jens Axboe <jens.axboe@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
---
Unless someone objects, Andrew, can you please take this patch?
Thanks.
fs/super.c | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/fs/super.c b/fs/super.c
index 69688b1..1ada607 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -575,6 +575,11 @@ int do_remount_sb(struct super_block *sb, int flags, void *data, int force)
return 0;
}
+/*
+ * For emergency remount
+ */
+static struct workqueue_struct *emergency_remount_wq;
+
static void do_emergency_remount(struct work_struct *work)
{
struct super_block *sb, *n;
@@ -605,13 +610,25 @@ void emergency_remount(void)
{
struct work_struct *work;
+ if (!emergency_remount_wq)
+ return;
+
work = kmalloc(sizeof(*work), GFP_ATOMIC);
if (work) {
INIT_WORK(work, do_emergency_remount);
- schedule_work(work);
+ queue_work(emergency_remount_wq, work);
}
}
+static int __init emergency_remount_init(void)
+{
+ emergency_remount_wq = create_singlethread_workqueue("emerg-remount");
+ if (!emergency_remount_wq)
+ pr_warn("failed to create emergency remount workqueue\n");
+ return 0;
+}
+subsys_initcall(emergency_remount_init);
+
/*
* Unnamed block devices are dummy devices used by virtual
* filesystems which don't use real block-devices. -- jrs
next prev parent reply other threads:[~2010-05-27 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:01 Change to invalidate_bdev() may break emergency remount R/O David Howells
2010-05-27 9:57 ` Tejun Heo [this message]
2010-05-27 14:59 ` [PATCH] fs: run emergency remount on dedicated workqueue Américo Wang
2010-05-27 17:03 ` Tejun Heo
2010-05-28 6:46 ` Américo Wang
2010-06-01 23:46 ` Andrew Morton
2010-06-01 23:57 ` Linus Torvalds
2010-06-02 0:13 ` Tejun Heo
2010-06-02 1:02 ` Dave Young
2010-06-02 1:57 ` Andrew Morton
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=4BFE4203.5010803@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--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).