From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>,
Szabolcs Szakacsits <szaka@ntfs-3g.org>,
ntfs-3g-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
ext2-devel@lists.sourceforge.net, zfs-fuse@googlegroups.com,
Marc Andre Tanner <mat@brain-dump.org>,
Jean-Pierre ANDRE <jean-pierre.andre@wanadoo.fr>
Subject: Re: [ANNOUNCEMENT] Linux POSIX file system test suite
Date: Mon, 7 Apr 2008 12:07:05 +1000 [thread overview]
Message-ID: <20080407020705.GY108924158@sgi.com> (raw)
In-Reply-To: <20080404154818.GA7710@infradead.org>
On Fri, Apr 04, 2008 at 11:48:18AM -0400, Christoph Hellwig wrote:
> On Fri, Apr 04, 2008 at 04:51:09PM +1000, David Chinner wrote:
> > expect 0 symlink ${name256} ${n0}
> > expect 0 unlink ${n0}
> >
> > Test 6 is failing with ENAMETOOLONG
> > Test 7 is failing (correctly) with ENOENT because test 6 failed.
> >
> > So there's only one failure here, and that is that that we're rejecting
> > ${name256} as too long. I think that getname() is doing this. Seems sane
> > to me to disallow symlinking to pathnames that can't be constructed,
> > even if POSIX apparently allows it.
>
> i'd rather expect this to be the component validation in xfs_symlink.
> It's superflous and not done by any other fiesystem.
Ah yes, you are right - PATH_MAX != NAME_MAX...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-07 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 21:29 [ANNOUNCEMENT] Linux POSIX file system test suite Szabolcs Szakacsits
2008-04-02 22:23 ` Joel Becker
2008-04-03 4:12 ` Szabolcs Szakacsits
[not found] ` <Pine.LNX.4.62.0804030705050.12223-03lVS0d9f+JcfUEgzQKStNHuzzzSOjJt@public.gmane.org>
2008-04-03 16:48 ` Joel Becker
2008-04-03 16:51 ` Amar S. Tumballi
2008-04-03 18:27 ` Badari Pulavarty
[not found] ` <1207247251.30407.59.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
2008-04-06 23:34 ` Szabolcs Szakacsits
2008-04-07 17:04 ` Badari Pulavarty
2008-04-08 15:37 ` ext4 not updating ctime on truncate ? Badari Pulavarty
2008-04-08 15:40 ` Eric Sandeen
2008-04-04 0:33 ` [ANNOUNCEMENT] Linux POSIX file system test suite David Chinner
2008-04-04 6:51 ` David Chinner
2008-04-04 15:48 ` Christoph Hellwig
2008-04-07 2:07 ` David Chinner [this message]
[not found] ` <20080404065109.GW108924158-sJ/iWh9BUns@public.gmane.org>
2008-04-06 23:51 ` Szabolcs Szakacsits
2008-04-04 20:40 ` Marc Andre Tanner
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=20080407020705.GY108924158@sgi.com \
--to=dgc@sgi.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=jean-pierre.andre@wanadoo.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mat@brain-dump.org \
--cc=ntfs-3g-devel@lists.sourceforge.net \
--cc=szaka@ntfs-3g.org \
--cc=zfs-fuse@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.