All of lore.kernel.org
 help / color / mirror / Atom feed
From: ZhangZhen <zhenzhang.zhang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: <sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Du Yongfeng
	<du.duyongfeng-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: [PATCH] cifs: new helper: file_inode(file)
Date: Thu, 6 Mar 2014 12:01:03 +0800	[thread overview]
Message-ID: <5317F2FF.9020609@huawei.com> (raw)
In-Reply-To: <5316EE49.6090409-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

cifs: new helper: file_inode(file)

Signed-off-by: Zhang Zhen <zhenzhang.zhang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
---
 fs/cifs/ioctl.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/cifs/ioctl.c b/fs/cifs/ioctl.c
index 7749230..45cb59b 100644
--- a/fs/cifs/ioctl.c
+++ b/fs/cifs/ioctl.c
@@ -85,7 +85,7 @@ static long cifs_ioctl_clone(unsigned int xid, struct file *dst_file,
 		goto out_fput;
 	}

-	src_inode = src_file.file->f_dentry->d_inode;
+	src_inode = file_inode(src_file.file);

 	/*
 	 * Note: cifs case is easier than btrfs since server responsible for
-- 
1.8.1.4


.




_______________________________________________
kernel.openeuler mailing list
kernel.openeuler-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
http://rnd-openeuler.huawei.com/mailman/listinfo/kernel.openeuler

       reply	other threads:[~2014-03-06  4:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5316EE49.6090409@huawei.com>
     [not found] ` <5316EE49.6090409-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-03-06  4:01   ` ZhangZhen [this message]
     [not found]     ` <5317F2FF.9020609-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-03-27  8:49       ` [PATCH] cifs: new helper: file_inode(file) ZhangZhen

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=5317F2FF.9020609@huawei.com \
    --to=zhenzhang.zhang-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=du.duyongfeng-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.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.