From: "J. Bruce Fields" <bfields@fieldses.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: Re: [PATCH] Export __locks_copy_lock() so modular lockd builds
Date: Fri, 25 Apr 2008 19:03:36 -0400 [thread overview]
Message-ID: <20080425230336.GC9597@fieldses.org> (raw)
In-Reply-To: <adar6ct5zvw.fsf@cisco.com>
On Fri, Apr 25, 2008 at 03:32:51PM -0700, Roland Dreier wrote:
> Commit 1a747ee0 ("locks: don't call ->copy_lock methods on return of
> conflicting locks") changed fs/lockd/svclock.c to call
> __locks_copy_lock() instead of locks_copy_lock(), but lockd can be built
> as a module and __locks_copy_lock() is not exported, which causes a
> build error
>
> ERROR: "__locks_copy_lock" [fs/lockd/lockd.ko] undefined!
>
> with CONFIG_LOCKD=m.
>
> Fix this by exporting __locks_copy_lock().
Oog, sorry. Thaks for the fix!
>
> Signed-off-by: Roland Dreier <rolandd@cisco.com>
Acked-by: J. Bruce Fields <bfields@citi.umich.edu>
> ---
> fs/locks.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/locks.c b/fs/locks.c
> index e1ea2fe..44d9a6a 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -236,6 +236,7 @@ void __locks_copy_lock(struct file_lock *new, const struct file_lock *fl)
> new->fl_ops = NULL;
> new->fl_lmops = NULL;
> }
> +EXPORT_SYMBOL(__locks_copy_lock);
>
> void locks_copy_lock(struct file_lock *new, struct file_lock *fl)
> {
prev parent reply other threads:[~2008-04-25 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 22:32 [PATCH] Export __locks_copy_lock() so modular lockd builds Roland Dreier
2008-04-25 23:03 ` J. Bruce Fields [this message]
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=20080425230336.GC9597@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=torvalds@linux-foundation.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.