Re: old bug: mount_nfs path/name is limited to 88 chars

From: Anton Shterenlikht <mexas_at_bris.ac.uk>
Date: Mon, 19 Jan 2015 07:44:26 -0800 (PST)
>From rmacklem_at_uoguelph.ca Mon Jan 19 15:37:25 2015
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105
>> 
>> is a show stopper for me. The path/name length is
>> beyond my control, so I cannot make it shorter.
>> 
>> This discussion seems inconclusive:
>> http://lists.freebsd.org/pipermail/freebsd-hackers/2012-April/038543.html
>> 
>> Is there no easy solution to this PR?
>> Or is there no interest in fixing the issue?
>> 
>Well, the "easy" solution is to just increase the value
>of NNAMELEN and rebuild everything from sources to use
>the modified sys/mount.h. (If you can run a modified
>system built entirely from sources, I think you can do
>this.)

I can do this on several 10.1-stable systems, but I understood
from the email trail that there is no guarantee that nothing
will be broken by such change. I know there is never a guarantee,
but..

>However, this can't be done in -current because it breaks
>the statfs(2) syscall API, etc.

Even on 10.1-stable I see in statfs(2):

     #define MNAMELEN        88              /* size of on/from name bufs */

So perhaps changing MNAMELEN will break statfs(2) on
-stable too?

Anton
Received on Mon Jan 19 2015 - 14:44:57 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:55 UTC