From: NeilBrown <neilb@suse.de>
To: Josef Bacik <jbacik@fb.com>, Chris Mason <clm@fb.com>,
Jan Kara <jack@suse.cz>, David Sterba <dsterba@suse.cz>,
Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] make BTRFS, UDF, NILFS2 work with NFSv2.
Date: Fri, 08 May 2015 10:16:23 +1000 [thread overview]
Message-ID: <20150508001142.31129.7604.stgit@notabene.brown> (raw)
Hi filesystem folks,
I just had a report that BTRFS doesn't work reliably with NFSv2.
The problem is that NFSv2 doesn't encode filehandle size so it may
report to the filesystem a longer handle that is being expected.
Filesystems should not require a specific length, only at least that
length.
A code audit shows that NILFS2 and UDF suffer the same problem.
Following patches should fix it... well, they compile and look good.
Please consider for inclusion is respective trees.
Admittedly NFSv2 is a bit "last century", but while it is easy to
support, we may as well.
Thanks,
NeilBrown
---
NeilBrown (3):
BTRFS: support NFSv2 export
NILFS2: support NFSv2 export
UDF: support NFSv2 export
fs/btrfs/export.c | 10 +++++-----
fs/nilfs2/namei.c | 6 +++---
fs/udf/namei.c | 16 ++++++++++++----
3 files changed, 20 insertions(+), 12 deletions(-)
--
Signature
next reply other threads:[~2015-05-08 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 0:16 NeilBrown [this message]
2015-05-08 0:16 ` [PATCH 3/3] UDF: support NFSv2 export NeilBrown
[not found] ` <20150508001623.31129.24710.stgit-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2015-05-11 8:57 ` Jan Kara
[not found] ` <20150508001142.31129.7604.stgit-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2015-05-08 0:16 ` [PATCH 1/3] BTRFS: " NeilBrown
2015-05-11 8:13 ` David Sterba
2015-09-24 1:59 ` Neil Brown
2015-10-05 14:32 ` Chris Mason
2015-05-08 0:16 ` [PATCH 2/3] NILFS2: " NeilBrown
[not found] ` <20150508001623.31129.25102.stgit-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2015-05-10 16:31 ` Ryusuke Konishi
2015-05-11 7:02 ` NeilBrown
2015-05-11 9:54 ` Ryusuke Konishi
2015-05-11 11:13 ` [PATCH v2] " NeilBrown
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=20150508001142.31129.7604.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@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;
as well as URLs for NNTP newsgroup(s).