From: Peng Tao <bergwolf@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Peng Tao <bergwolf@gmail.com>,
Patrick Farrell <paf@cray.com>,
Andreas Dilger <andreas.dilger@intel.com>
Subject: [PATCH v2 01/12] Revert "staging/lustre/nfs: writing to new files will return ENOENT"
Date: Tue, 26 Nov 2013 23:04:35 +0800 [thread overview]
Message-ID: <1385478286-5525-2-git-send-email-bergwolf@gmail.com> (raw)
In-Reply-To: <1385478286-5525-1-git-send-email-bergwolf@gmail.com>
This reverts commit ad8dbc93a464869f64365a2123b3491965df3b3e.
The original commit was reverted in Lustre tree this due to
interoperability problems with 2.1 servers. But I forgot to remove
it from my patch queue. sorry for the noise.
Cc: Patrick Farrell <paf@cray.com>
Cc: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Peng Tao <bergwolf@gmail.com>
---
drivers/staging/lustre/lustre/llite/file.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/llite/file.c b/drivers/staging/lustre/lustre/llite/file.c
index f36c5d8..82248e9 100644
--- a/drivers/staging/lustre/lustre/llite/file.c
+++ b/drivers/staging/lustre/lustre/llite/file.c
@@ -368,6 +368,8 @@ static int ll_intent_file_open(struct file *file, void *lmm,
{
struct ll_sb_info *sbi = ll_i2sbi(file->f_dentry->d_inode);
struct dentry *parent = file->f_dentry->d_parent;
+ const char *name = file->f_dentry->d_name.name;
+ const int len = file->f_dentry->d_name.len;
struct md_op_data *op_data;
struct ptlrpc_request *req;
__u32 opc = LUSTRE_OPC_ANY;
@@ -392,9 +394,8 @@ static int ll_intent_file_open(struct file *file, void *lmm,
}
op_data = ll_prep_md_op_data(NULL, parent->d_inode,
- file->f_dentry->d_inode, NULL, 0,
+ file->f_dentry->d_inode, name, len,
O_RDWR, opc, NULL);
-
if (IS_ERR(op_data))
return PTR_ERR(op_data);
--
1.7.9.5
next prev parent reply other threads:[~2013-11-26 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 15:04 [PATCH v2 00/12] staging/lustre: sync with extern tree, set 2 Peng Tao
2013-11-26 15:04 ` Peng Tao [this message]
2013-11-26 15:04 ` [PATCH v2 02/12] staging/lustre/llog: MGC to use OSD API for backup logs Peng Tao
2013-11-26 18:33 ` Levente Kurusa
2013-11-26 15:04 ` [PATCH v2 03/12] staging/lustre: constify uuid argument of obd_uuid2str Peng Tao
2013-11-26 15:04 ` [PATCH v2 04/12] staging/lustre: make obd_uuid_equals return bool Peng Tao
2013-11-26 15:04 ` [PATCH v2 05/12] staging/lustre/scrub: OI scrub on OST Peng Tao
2013-11-26 15:04 ` [PATCH v2 06/12] staging/lustre: make code align in lma_incompat Peng Tao
2013-11-26 15:04 ` [PATCH v2 07/12] staging/lustre/llite: don't check for O_CREAT in it_create_mode Peng Tao
2013-11-26 15:04 ` [PATCH v2 08/12] staging/lustre/build: clean up unused variables and dead code Peng Tao
2013-11-26 15:04 ` [PATCH v2 09/12] staging/lustre/build: fix compilation issue with is_compat_task Peng Tao
2013-11-26 15:04 ` [PATCH v2 10/12] staging/lustre/ptlrpc: Fix a crash when dereferencing NULL pointer Peng Tao
2013-11-26 15:04 ` [PATCH v2 11/12] staging/lustre/hsm: Add hsm_release feature Peng Tao
2013-11-26 15:04 ` [PATCH v2 12/12] staging/lustre/llite: extended attribute cache Peng Tao
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=1385478286-5525-2-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paf@cray.com \
/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.