Bug 761749 (GLUSTER-17) - remove posix NAME_MAX
Summary: remove posix NAME_MAX
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-17
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-16 09:23 UTC by Vikas Gorur
Modified: 2010-01-28 13:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Vikas Gorur 2009-06-16 09:23:24 UTC
Migrated from rt #338.

History:

Tue Sep 16 08:02:41 2008  	 avati - Ticket created  	 	 
Subject: 	remove posix NAME_MAX

statvfs call provides a member f_namemax which is the max filename
length of the filesystem. posix should findout the namemax in a
statvfs() call in init and use that instead of NAME_MAX macro.

#   	Tue Sep 16 10:12:18 2008 	ab - Correspondence 

GNU standard is to not have any limit at all. It should be dynamically
allocated. If possible, we should use GNU standard.

On Tue Sep 16 08:02:41 2008, avati wrote:
> statvfs call provides a member f_namemax which is the max filename
> length of the filesystem. posix should findout the namemax in a
> statvfs() call in init and use that instead of NAME_MAX macro.

#   	Mon Mar 23 16:20:09 2009 	gowda - Correspondence 

What is the final conclusion on this? Are we going to have limits or not?

Comment 1 Basavanagowda Kanur 2009-07-06 08:28:55 UTC
for now we will continue using NAME_MAX.

moving to statvfs() based dynamic namemax will require lot of changes to code-base at very less advantage gained.

--
Gowda


Note You need to log in before you can comment on or make changes to this bug.