Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Apr 2018 15:02:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 227635] Increase MAXPATHLEN value
Message-ID:  <bug-227635-227-gfJgU8Ihcp@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-227635-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-227635-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227635

Conrad Meyer <cem@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cem@freebsd.org

--- Comment #2 from Conrad Meyer <cem@freebsd.org> ---
This shouldn't be done solely for a piece of broken ports software.  This i=
s a
big change, not to mention ABI-breaking.  It can't go to stable/* but the p=
ort
needs to work on stable/*, presumably.

The supplied patch also isn't sufficient to fix up the fallout (particularl=
y,
libc glob allocates a bunch of MAXPATHLEN buffers on the stack, which becom=
es
much worse with a 4kB length).

Here is a little more thorough treatment of the issue:
https://reviews.freebsd.org/D12330 (it also bumps MAXNAMLEN from 255 to 102=
3 =E2=80=94
long enough to hold 255 arbitrary Unicode characters in UTF-8).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227635-227-gfJgU8Ihcp>