From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/7] NFS: Make nfs_llseek methods consistent
Date: Tue, 10 Jun 2008 14:27:00 -0400 [thread overview]
Message-ID: <1213122420.20459.2.camel@localhost> (raw)
In-Reply-To: <20080527202915.6651.44947.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
On Tue, 2008-05-27 at 16:29 -0400, Chuck Lever wrote:
> Clean up: Report the same debugging info in nfs_llseek_dir() and
> nfs_llseek_file().
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> fs/nfs/dir.c | 12 ++++++++++--
> fs/nfs/file.c | 7 +++++++
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
>
> diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
> index 1bc8bc6..36e51f7 100644
> --- a/fs/nfs/dir.c
> +++ b/fs/nfs/dir.c
> @@ -603,7 +603,15 @@ out:
>
> static loff_t nfs_llseek_dir(struct file *filp, loff_t offset, int origin)
> {
> - mutex_lock(&filp->f_path.dentry->d_inode->i_mutex);
> + struct dentry *dentry = filp->f_path.dentry;
> + struct inode *inode = filp->f_path.dentry->d_inode;
> +
> + dfprintk(VFS, "NFS: llseek dir(%s/%s, %lld, %d)\n",
> + dentry->d_parent->d_name.name,
> + dentry->d_name.name,
> + offset, origin);
> +
> + mutex_lock(&inode->i_mutex);
> switch (origin) {
> case 1:
> offset += filp->f_pos;
> @@ -619,7 +627,7 @@ static loff_t nfs_llseek_dir(struct file *filp, loff_t offset, int origin)
> nfs_file_open_context(filp)->dir_cookie = 0;
> }
> out:
> - mutex_unlock(&filp->f_path.dentry->d_inode->i_mutex);
> + mutex_unlock(&inode->i_mutex);
> return offset;
> }
>
> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
> index e452903..06a1322 100644
> --- a/fs/nfs/file.c
> +++ b/fs/nfs/file.c
> @@ -170,6 +170,13 @@ force_reval:
>
> static loff_t nfs_file_llseek(struct file *filp, loff_t offset, int origin)
> {
> + struct dentry *dentry = filp->f_path.dentry;
> +
> + dfprintk(VFS, "NFS: llseek file(%s/%s, %lld, %d)\n",
> + dentry->d_parent->d_name.name,
> + dentry->d_name.name,
> + offset, origin);
> +
This will result in 'unused variable' warnings for 'dentry' if you
compile with #undef RPC_DEBUG.
> /* origin == SEEK_END => we must revalidate the cached file length */
> if (origin == SEEK_END) {
> struct inode *inode = filp->f_mapping->host;
>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2008-06-10 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 20:28 [PATCH 0/7] Second series of patches for 2.6.27 Chuck Lever
[not found] ` <20080527202347.6651.54668.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-05-27 20:29 ` [PATCH 1/7] NFS: Make nfs_fsync methods consistent Chuck Lever
2008-05-27 20:29 ` [PATCH 2/7] NFS: Make nfs_llseek " Chuck Lever
[not found] ` <20080527202915.6651.44947.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-10 18:27 ` Trond Myklebust [this message]
2008-05-27 20:29 ` [PATCH 3/7] NFS: Make nfs_open " Chuck Lever
[not found] ` <20080527202922.6651.18161.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-10 18:27 ` Trond Myklebust
2008-05-27 20:29 ` [PATCH 4/7] NFS: Add debugging facility for NFS aops Chuck Lever
[not found] ` <20080527202929.6651.32893.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-10 18:30 ` Trond Myklebust
2008-05-27 20:29 ` [PATCH 5/7] NFS: Use NFSDBG_FILE for all fops Chuck Lever
[not found] ` <20080527202937.6651.55382.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-10 18:32 ` Trond Myklebust
2008-05-27 20:29 ` [PATCH 6/7] NFS: Fix trace debugging nits in write.c Chuck Lever
2008-05-27 20:29 ` [PATCH 7/7] SUNRPC: Remove obsolete messages during transport connect Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 21:55 [PATCH 0/7] dprintk clean-ups [resend] Chuck Lever
[not found] ` <20080611215018.7068.71737.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-11 21:55 ` [PATCH 2/7] NFS: Make nfs_llseek methods consistent Chuck Lever
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=1213122420.20459.2.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.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