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

Garrett Cooper yaneurabeya at gmail.com
Mon Jan 19 21:20:42 UTC 2015


On Jan 19, 2015, at 8:46, Brandon Allbery <allbery.b at gmail.com> wrote:

> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht <mexas at bris.ac.uk>
> wrote:
> 
>> So perhaps changing MNAMELEN will break statfs(2) on
>> -stable too?
>> 
> 
> I believe the context there is not so much "-current is special", as
> "changing it for everyone is bad news" (and this would necessarily need to
> originate in -current).

A compat layer needs to be created for all of the affected syscalls, and the change needs to be made. That’s it in a nutshell.

Doing it in 11 makes sense since there is a compat layer for 10 now… if I knew all of the steps I would happily do them as annoys me from time to time as well with the path length issue.

Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20150119/c0a7e57d/attachment.sig>


More information about the freebsd-current mailing list