On Thu, 2013-07-18 at 19:30 -0400, Rick Macklem wrote:
> Andre Heider wrote:
> > On Wed, Jul 17, 2013 at 11:59 PM, Trond Myklebust
> > <Trond.Myklebust@xxxxxxxxxx> wrote:
> > > Technically, the Linux client is allowed by the NFSv4 spec to send
> > > 3 word bitmaps as part of an OPEN request. However, this causes the
> > > current FreeBSD server to return NFS4ERR_ATTRNOTSUPP errors.
> > >
> > > Fix the regression by making the Linux client use a 2 word bitmap
> > > unless
> > > doing NFSv4.2 with labeled NFS.
> > >
> > > Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
> >
> > Tested-by: Andre Heider <a.heider@xxxxxxxxx>
> >
> I've attached the patch I plan to commit to FreeBSD's head soon, which
> fixes the server so that it checks for the high order bitmaps words
> being non-zero before replying with NFS4_ERR_ATTRNOTSUPP.
>
> The patch is pretty straightforward, but if you can apply it to your
> server and test it against the unpatched Linux client, that would be
> appreciated.
>
> It will take a while for the patch to find its way to a FreeBSD release,
> so having the workaround in the Linux client will be very helpful.
Right. So, my plan is to send patch 1/2 as a bugfix within the next few
days, to ensure that we end up with no gap in NFSv4 client functionality
between the release versions of Linux 3.10 and 3.11.
Since 2/2 is more of a cleanup, and actually changes the functionality
to send only a 1-word bitmap for truncate() calls, I'll wait for the
3.12 merge window before committing that.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
