linux-kernel - Re: [git pull] VFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <B0CB85F7-23A7-45EA-848E-8B2701545371@mit.edu>
Date:	Wed, 16 Mar 2011 07:46:40 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Dave Chinner <david@...morbit.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [git pull] VFS - the first pile

On Mar 16, 2011, at 3:21 AM, Al Viro wrote:

> BTW, you want to update 005 in there - we are back to correct "maximum
> is 40 symlinks total, 8 levels on nesting" for all syscalls.  Add the
> 41st symlink to your chain in testcase ;-)

Unless there's a way to read out these limits, I'm not sure it's a good idea
to add a test like that to xfstests --- it's too fragile since at some point
we might change what those limits might be.

Also, xfstests is primarily intended to be a file system level stress tester
testing for correctness, and issues of whether we blow up on the 40th, 
41st, or 42nd symlink seems more like an ABI issue --- and even there I'm
not sure the ABI specification should be quite that detailed over what's
allowed and not allowed.

-- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/