From: Christoph Hellwig <hch@infradead.org>
To: Chris Walker <christopher.walker@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: quick question about filename length
Date: Sat, 16 May 2009 16:25:11 -0400 [thread overview]
Message-ID: <20090516202511.GA28186@infradead.org> (raw)
In-Reply-To: <554e24be0905161106x6a62b7bldc65325ac4102628@mail.gmail.com>
On Sat, May 16, 2009 at 02:06:22PM -0400, Chris Walker wrote:
> Thanks for you quick reply, Eric.
>
> I have a user who is having filenames (path+filename) cut off at 255
> characters midway through a simulation -- but the problem must be
> elsewhere
XFS doesn't actually see the whole filename in normal operation (except
for copying out the data out of symbolic links), as the resolution to
individual components is done by the VFS. Long file name should work
just fine on Linux and do in my test. Maybe some buffer is sized using
incorrect in userspace?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-16 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 16:15 quick question about filename length Chris Walker
2009-05-16 17:04 ` Eric Sandeen
2009-05-16 18:06 ` Chris Walker
2009-05-16 20:25 ` Christoph Hellwig [this message]
2009-05-16 21:42 ` Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090516202511.GA28186@infradead.org \
--to=hch@infradead.org \
--cc=christopher.walker@gmail.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox