From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: 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: Fri, 4 Apr 2008 11:48:18 -0400 [thread overview]
Message-ID: <20080404154818.GA7710@infradead.org> (raw)
In-Reply-To: <20080404065109.GW108924158@sgi.com>
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.
next prev parent reply other threads:[~2008-04-04 15:48 UTC|newest]
Thread overview: 14+ 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-04 0:33 ` David Chinner
2008-04-04 6:51 ` David Chinner
2008-04-04 15:48 ` Christoph Hellwig [this message]
2008-04-07 2:07 ` David Chinner
[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=20080404154818.GA7710@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fuse-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).