Date: Tue, 12 Sep 2017 23:23:56 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Ben RUBSON <ben.rubson@gmail.com> Cc: cem@freebsd.org, "freebsd-fs@freebsd.org" <freebsd-fs@FreeBSD.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: extending the maximum filename length (pointer to patch)[request for input] Message-ID: <C5F7C195-EC69-4B04-A13C-09DD5485DEEA@ultra-secure.de> In-Reply-To: <041393BA-94E3-4D22-95C8-EF0634746DC3@gmail.com> 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> <041393BA-94E3-4D22-95C8-EF0634746DC3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 12.09.2017 um 23:11 schrieb Ben RUBSON <ben.rubson@gmail.com>: > > 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). >>> >>> 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? >>> >>> 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. >>> >>> 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, >> >> 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=184340 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184340>; > 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 And there’s also this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215067 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215067>; "g_dev_taste: make_dev_p() failed on importing pool with snapshots with long names“ But maybe that has nothing to do with it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C5F7C195-EC69-4B04-A13C-09DD5485DEEA>