[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <922c4a440b455d158729abcc0c9f78dc3726c2c0.camel@themaw.net>
Date: Tue, 15 Feb 2022 15:00:29 +0800
From: Ian Kent <raven@...maw.net>
To: NeilBrown <neilb@...e.de>
Cc: autofs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.1.8 release
On Tue, 2022-02-15 at 09:46 +1100, NeilBrown wrote:
> On Mon, 14 Feb 2022, Ian Kent wrote:
> > On Thu, 2022-02-10 at 08:59 +1100, NeilBrown wrote:
> > > On Tue, 19 Oct 2021, Ian Kent wrote:
> > > > Hi all,
> > > >
> > > > It's time for a release, autofs-5.1.8.
> > > >
> > > ...
> > > > - also require TCP_REQUESTED when setting NFS port.
> > >
> > > Unfortunately that last patch is buggy. TCP_REQUESTED is masked
> > > out
> > > in
> > > the caller.
> >
> > Mmm ... sounds like I've made a mistake there.
> > I'll need to sort that out, thanks for pointing it out.
> >
> > >
> > > Maybe the following is best.
> > >
> > > NeilBrown
> > >
> > > From: NeilBrown <neilb@...e.de>
> > > Subject: [PATCH] Test TCP request correctly in nfs_get_info()
> > >
> > > The TCP_REQUESTED flag is masked out by the caller, so it never
> > > gets
> > > to
> > > nfs_get_info().
> >
> > That wasn't my intent, I'll need to look at it again.
> > The case I'm trying to cover is fairly specific so I will need to
> > look at it again.
> >
>
> I'm curious: What was the case you were trying to solve?? I couldn't
> guess any justification for the change.
Somewhere along the way I broke NFSv4 mounts being able to be mounted
without the use of rpcbind.
I require the option fstype=nfs4 for this and if given the map entry
should be mountable without recall to any other services beside NFS.
So that option shouldn't be masked out since it allows automount
to identify (or should) this case.
Ian
Powered by blists - more mailing lists