Date: Tue, 12 Sep 2017 23:11:52 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: cem@freebsd.org Cc: "freebsd-fs@freebsd.org" <freebsd-fs@FreeBSD.org>, freebsd-current <freebsd-current@freebsd.org>, Julian Elischer <julian@freebsd.org> Subject: Re: extending the maximum filename length (pointer to patch)[request for input] Message-ID: <041393BA-94E3-4D22-95C8-EF0634746DC3@gmail.com> In-Reply-To: <da31a2a2-03ea-47ac-4238-c97ad563e54c@freebsd.org> References: <0154558d-b2ad-af97-3960-3e392678f709@freebsd.org> <CAG6CVpXxr%2B7j6dN0EUhQ95Rn9GQtakJOsAKCCyBoUJjfUU16Hw@mail.gmail.com> <8d04540b-6daf-aa13-5648-0ec2541cbae6@freebsd.org> <CAG6CVpWe5bUkU1CkpoSmeZ0jxH%2BKb67fy7VE=Lq7guBBTzeCJw@mail.gmail.com> <da31a2a2-03ea-47ac-4238-c97ad563e54c@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/9/17 2:17 pm, Conrad Meyer wrote: > On Sat, Sep 9, 2017 at 9:09 AM, Julian Elischer <julian@freebsd.org> = wrote: >> maybe we could get it into -current. >> It'd be silly to have to have people re-inventing hte wheel all the = time. >> How about you put those changes into the reviews.freebsd.org and we = can get >> some general consensus on them. >> We'll have to do similar for the Asian customers and anyone who uses = UTF-8. >> So it >> would be silly to have to develop it all again (but subtly different = of >> course). >>=20 >> The key issue is how many system calls and other APIs would be = broken, >> and how many would be broken in a non backwards compatible way? >>=20 >> We would need it in a stable/10 and 11 branch but if the patch is = isolated >> enough we could carry it forward until we get to 12. >>=20 >> One has to allow people to do whatever they are used to with Windows. >> And in this case the issue is serving files over samba to windows = machines. > Hey Julian, >=20 > I've thrown the patch up at https://reviews.freebsd.org/D12330 . I > haven't actually tested it on FreeBSD, but it does compile. We also > have some patches against contrib/pjdfstest to fix those tests against > long file names, but I think we can hold off on those changes until > we've nailed down what the architectural change will be (if any). Hi Conrad, This patch makes me think about another related bug #184340 : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D184340 It is about PATH_MAX which in some cases can be too small. Not sure if it's the case / and how to do it, but perhaps it is time to raise some other limits / think about a global solution regarding these length limits ? Many thanks ! Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?041393BA-94E3-4D22-95C8-EF0634746DC3>