Re: bin/57103: ls prints error message with autofs

[Michael van Elst <mlelstv%serpens.de@localhost>]

The following reply was made to PR bin/57103; it has been noted by GNATS.

From: Michael van Elst <mlelstv%serpens.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, mlelstv%netbsd.org@localhost
Subject: Re: bin/57103: ls prints error message with autofs
Date: Sun, 11 Dec 2022 14:03:51 +0100

 On Sun, Dec 11, 2022 at 12:45:01PM +0000, Robert Elz wrote:
 > 
 >      Date:        Sun, 11 Dec 2022 10:10:01 +0000 (UTC)
 >      From:        mlelstv%serpens.de@localhost (Michael van Elst)
 >      Message-ID:  <20221211101001.62C331A9239%mollari.NetBSD.org@localhost>
 >  
 >    |  Either autofs should learn the pathconf operation or ls should learn
 >    |  that the error EOPNOTSUPP for this operation should be handled silently.
 >  
 >  Probably both.
 
 I've committed a fix to autofs to use genfs_pathconf().
 
 Unlike FreeBSD, we fall back to return EOPNOSUPP if a filesystem
 hasn't implemented a method. FreeBSD has individual defaults for
 each method (mostly the 'generic' implementations) and the
 default for vop_pathconf is to return EINVAL unconditionally.
 
 N.B. mfs calls genfs_badop, i.e. triggers a panic. This should probably
 be changed.
 
 Greetings,
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."