linux-kernel - [PATCH 0/3] make BTRFS, UDF, NILFS2 work with NFSv2.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150508001142.31129.7604.stgit@notabene.brown>
Date:	Fri, 08 May 2015 10:16:23 +1000
From:	NeilBrown <neilb@...e.de>
To:	Josef Bacik <jbacik@...com>, Chris Mason <clm@...com>,
	Jan Kara <jack@...e.cz>, David Sterba <dsterba@...e.cz>,
	Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>
Cc:	linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
	linux-nilfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-btrfs@...r.kernel.org
Subject: [PATCH 0/3] make BTRFS, UDF, NILFS2 work with NFSv2.

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/