From: Ingo Molnar <mingo@elte.hu>
To: David Howells <dhowells@redhat.com>
Cc: nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
cluster-devel@redhat.com, torvalds@osdl.org,
linux-cachefs@redhat.com, jens.axboe@oracle.com,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-cifs-client@lists.samba.org
Subject: Re: [PATCH] SLOW_WORK: Fix the CONFIG_MODULES=n case
Date: Tue, 1 Dec 2009 15:26:11 +0100 [thread overview]
Message-ID: <20091201142611.GA1183@elte.hu> (raw)
In-Reply-To: <25668.1259675528@redhat.com>
* David Howells <dhowells@redhat.com> wrote:
> @@ -943,6 +953,7 @@ EXPORT_SYMBOL(slow_work_register_user);
> */
> static void slow_work_wait_for_items(struct module *module)
> {
> +#ifdef CONFIG_MODULES
> DECLARE_WAITQUEUE(myself, current);
> struct slow_work *work;
> int loop;
> @@ -989,6 +1000,7 @@ static void slow_work_wait_for_items(struct module *module)
>
> remove_wait_queue(&slow_work_unreg_wq, &myself);
> mutex_unlock(&slow_work_unreg_sync_lock);
> +#endif /* CONFIG_MODULES */
> }
this slow_work_wait_for_items() function should move into the #ifdef
block too.
With that fixed it looks good to me for .33 (but i havent tested it):
Acked-by: Ingo Molnar <mingo@elte.hu>
In terms of .32 i guess it's OK too and the fix is needed - but i'd
really not have done even the preceding changes - why again did we need
/proc/slow_work_rq via 8fba10a and why did it have to happen right
before the final kernel?
If then it should have been done in debugfs - we dont need yet another
/proc ABI.
Also, a very small aesthetic detail: i think the title should use the
'slow-work: ' prefix, not 'SLOW_WORK: '.
Thanks,
Ingo
next prev parent reply other threads:[~2009-12-01 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 13:52 [PATCH] SLOW_WORK: Fix the CONFIG_MODULES=n case David Howells
2009-12-01 14:26 ` Ingo Molnar [this message]
2009-12-01 15:13 ` David Howells
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=20091201142611.GA1183@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=dhowells@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.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).