[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200921181123.GA1776@lst.de>
Date: Mon, 21 Sep 2020 20:11:23 +0200
From: Christoph Hellwig <hch@....de>
To: Anna Schumaker <anna.schumaker@...app.com>
Cc: Christoph Hellwig <hch@....de>,
Trond Myklebust <trond.myklebust@...merspace.com>,
Al Viro <viro@...iv.linux.org.uk>,
Richard Henderson <rth@...ddle.net>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Matt Turner <mattst88@...il.com>, linux-alpha@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>
Subject: Re: [PATCH 2/5] fs,nfs: lift compat nfs4 mount data handling into
the nfs code
On Mon, Sep 21, 2020 at 12:05:52PM -0400, Anna Schumaker wrote:
> This is for the binary mount stuff? That was already legacy code when
> I first started, and mount uses text options now. My preference is for
> keeping it as close to the original code as possible.
Ok. Al, are you fine with the series as-is then?
>
> I'm curious if you've been able to test this? I'm not sure if there is
> a way to force binary mount data through mount.nfs
The test is pretty trivial - even the most recent nfsutils supports the
binary mount data. You just need to patch out the detection for a
modern kernel.
Powered by blists - more mailing lists