From: Steven Whitehouse <swhiteho@redhat.com>
To: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Cc: Tejun Heo <tj@kernel.org>, Steven Whitehouse <swhiteho@redhat.com>
Subject: [PATCH 2/5] GFS2: WQ_NON_REENTRANT is meaningless and going away
Date: Mon, 19 Aug 2013 09:48:04 +0100 [thread overview]
Message-ID: <1376902087-7783-3-git-send-email-swhiteho@redhat.com> (raw)
In-Reply-To: <1376902087-7783-1-git-send-email-swhiteho@redhat.com>
From: Tejun Heo <tj@kernel.org>
dbf2576e37 ("workqueue: make all workqueues non-reentrant") made
WQ_NON_REENTRANT no-op and the flag is going away. Remove its usages.
This patch doesn't introduce any behavior changes.
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Cc: cluster-devel@redhat.com
diff --git a/fs/gfs2/main.c b/fs/gfs2/main.c
index e04d0e0..7b0f504 100644
--- a/fs/gfs2/main.c
+++ b/fs/gfs2/main.c
@@ -155,7 +155,7 @@ static int __init init_gfs2_fs(void)
goto fail_wq;
gfs2_control_wq = alloc_workqueue("gfs2_control",
- WQ_NON_REENTRANT | WQ_UNBOUND | WQ_FREEZABLE, 0);
+ WQ_UNBOUND | WQ_FREEZABLE, 0);
if (!gfs2_control_wq)
goto fail_recovery;
--
1.7.4
next prev parent reply other threads:[~2013-08-19 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 8:48 GFS2: Pre-pull patch posting (fixes) Steven Whitehouse
2013-08-19 8:48 ` [PATCH 1/5] GFS2: Fix typo in gfs2_create_inode() Steven Whitehouse
2013-08-19 8:48 ` Steven Whitehouse [this message]
2013-08-19 8:48 ` [PATCH 3/5] GFS2: don't overrun reserved revokes Steven Whitehouse
2013-08-19 8:48 ` [PATCH 4/5] GFS2: alloc_workqueue() doesn't return an ERR_PTR Steven Whitehouse
2013-08-19 8:48 ` [PATCH 5/5] GFS2: Check for glock already held in gfs2_getxattr Steven Whitehouse
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=1376902087-7783-3-git-send-email-swhiteho@redhat.com \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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 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).