Date: Thu, 5 Aug 2004 10:55:19 -0400 From: "Matt Emmerton" <matt@gsicomp.on.ca> To: <ilker.ozupak@emu.edu.tr>, <freebsd-hackers@freebsd.org> Subject: Re: Mount name length limit (MNAMELEN) Message-ID: <001b01c47afc$3c125c40$1200a8c0@gsicomp.on.ca> References: <20040804144019.83129.qmail@web51805.mail.yahoo.com> <200408051719.44705.ilker.ozupak@emu.edu.tr>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wednesday 04 August 2004 17:40, Patrick Dung wrote: > > Hi > > > > It seems that the constant is in /usr/sys/sys/mount.h. > > The limit is already there since the initial import in > > 1995. (From 4.4BSD?) > > I want to know what is the root cause preventing a > > larger value. > > > > PS: I have found some interesting links about > > MNAMELEN: > > > > http://leaf.dragonflybsd.org/mailarchive/kernel/2003-08/msg00194.html > > > > http://www.secnetix.de/~olli/FreeBSD/mnamelen.hawk I recall bringing this up on the FreeBSD lists a while ago (1-2 years?) and IIRC, the reason this is tough to change is that we use this constant in a lot of internal structures, and changing the constant will change the structure sizes which will break a lot of things. >From what I've seen in the Linux code, they never store a "char blah[MNAMELEN]" in their structures, but rather, a pointer to that data element (in the name cache, I think). Thus, they are free to change the size of the element without affecting the majority of structures that use it. -- Matt Emmerton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001b01c47afc$3c125c40$1200a8c0>