From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: green@linuxhacker.ru
Cc: devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Dmitry Eremin <dmitry.eremin@intel.com>
Subject: Re: [PATCH] staging/lustre: proper support of NFS anonymous dentries
Date: Sun, 14 Feb 2016 16:58:09 -0800 [thread overview]
Message-ID: <20160215005809.GA19643@kroah.com> (raw)
In-Reply-To: <1455495232-3270203-1-git-send-email-green@linuxhacker.ru>
On Sun, Feb 14, 2016 at 07:13:52PM -0500, green@linuxhacker.ru wrote:
> From: Dmitry Eremin <dmitry.eremin@intel.com>
>
> NFS can ask to encode dentries that are not connected to the root.
> The fix check for parent is NULL and encode a file handle accordingly.
>
> Reviewed-on: http://review.whamcloud.com/8347
> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4231
> Reviewed-by: Fan Yong <fan.yong@intel.com>
> Reviewed-by: James Simmons <uja.ornl@gmail.com>
> Reviewed-by: Jian Yu <jian.yu@intel.com>
> Signed-off-by: Dmitry Eremin <dmitry.eremin@intel.com>
> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
> ---
> This also happens to fix a crash when you try to use fhandle syscalls
> with Lustre.
>
> drivers/staging/lustre/lustre/llite/llite_nfs.c | 30 ++++++++++++++-----------
> include/linux/exportfs.h | 6 +++++
I need an ack from someone who maintains nfs code before I can take this
one...
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-15 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 0:13 [PATCH] staging/lustre: proper support of NFS anonymous dentries green
2016-02-15 0:58 ` Greg Kroah-Hartman [this message]
2016-02-23 2:34 ` Oleg Drokin
2016-02-26 6:13 ` Greg Kroah-Hartman
2016-02-26 6:13 ` Oleg Drokin
2016-02-26 6:24 ` Greg Kroah-Hartman
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=20160215005809.GA19643@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=dmitry.eremin@intel.com \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.