CVS log for src/tests/fs/vfs/t_vnops.c

Up to [cvs.NetBSD.org] / src / tests / fs / vfs

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Note exFAT also does not permit hard links

Add exFAT conditions to vfs tests

fix the grammar in comments reported by Jim Spath in misc/57397.

Test mkdir(2) with one or more trailing slashes - this currently fails
for v7fs.

fix typos in word "successfully", mainly s/succesfully/successfully/.

s/memry/memory+s/softare/software/+s/grapics/graphics+s/ouput/output

Sync with HEAD

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

PR kern/49033

POSIX allows for the atime (or technically, any of the times) to be
updated as a side effect of searching a directory (allows, not requires).
The NetBSD UDF implementation apparently works that way, treating a
directory search as a read of the directory, and hence updating the
access time.   Compensate for that in the test (rather than just
expecting failure) by verifying that the atime after the directory
search is within a small margin of the atime before the search
(currently, "small" is 1 second).   We could fetch the time before
the mkdir and both stat() calls, do all of that, fetch the time after,
subtract, and require the after stat() atime to be bounded by the atime
set by the original mkdir and returned in the first stat() and that time
+ the difference in elapsed time - that would be more accurate, but is
a lot more work for little real benefit.

Should anyone be interested in doing that extra work, remember to use
monotonic time (clock_gettime(CLOCK_MOMNOTONIC, ...)) not the time of day
clock for measuring the elapsed time.

Along with this, remove the "if (udf) failure expected" and the
if (udf && we haven't failed yet) fail("random failure failed to happen")
stuff...  (the "random" would have been that sometimes the mkdir and
two lookups (stat() calls) would all occur within the same clock tick,
meaning that the atimes would all be the same.  Other times the clock
would tick somewhere between the mkdir() and the 2nd stat().)

fix wrong variable.

- use snprintf
- print the argument that caused the error

The test for PR 50608 works now, remove the expected failure.

Don't use a filename with an embedded newline in the create_many test
case.  Instead, add a separate test case "create_nonalphanum" for
filenames containing non-alphanumeric characters.  The bug of
PR kern/50608 now causes a failure in create_nonalphanum rather than
create_many.

create_many: remove PR kern/50607 xfail

Seems to have been fixed by ext2fs_lookup.c 1.79
(thanks, riastradh)

create_many:
  * add xfails for ext2 and udf
  * don't try to create a subdirectory for sysvbfs

use a shorter filename template in previous (for v7fs)

Add a test which creates many directory entries.

Advisory locking for zfs.

Fix vattr_init_mask: mode is mode_t, not u_short.

Fixes fs/vfs/t_vnops:zfs_attrs test.

Tests claim rename(..., "x/.") yields EISDIR, so do that.  Fixes zfs.

Fix return code of rmdir(nonempty) in zfs: ENOTEMPTY, not EEXIST.

Make this run in NetBSD 6 by using st_mtimespec instead of st_mtim.

st_mtimespec is our traditional nonstandard name for what POSIX
called st_mtim in 2008, but these aren't going to run in non-NetBSD
anyway so using the nonstandard name shouldn't be an issue.

Pull up following revision(s) (requested by gson in ticket #424):
	tests/fs/vfs/t_vnops.c: revision 1.41
Mark udf_lookup_complex as an expected failure, referencing PR kern/49033.
Since it does not fail reliably, force it to fail to avoid spurious failure
reports due to unexpected success.

Test v7fs_lstat_symlink is no longer expected to fail.

Mark v7fs_lstat_symlink as an expected failure, referencing PR kern/48864.

Add a test of symlinks with long targets.

Rebase to HEAD as of a few days ago.

Mark udf_lookup_complex as an expected failure, referencing PR kern/49033.
Since it does not fail reliably, force it to fail to avoid spurious failure
reports due to unexpected success.

Rebase.

PR kern/49033: try to provide better diagnostics if the udf_lookup_complex
test randomly fails.

Add testcase that check lstat(2) values for symbolic links (PR
kern/48864).

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs.  ("Protocol error: too many arguments")

fix unused variable warnings

Check that rename(2) with NULL arguments fail with EFAULT.

Update test cases for UDF now udf_rename() uses the genfs_rename framework

Cover the last failing UDF test cases with a reference to PR kern/47986, i.e.
all rename's fail until UDF switches over to the new rename framework solving
the locking mechanism.

resync from head

Mark a bunch of routinely-broken ZFS tests as expected failures.  Point
them at PR kern/47656.

sync with head

Remove unneeded atf_tc_expect_pass calls.

Finish removing the block of commented-out code from rev 1.31

Hello, christos!

annotate fixed failures as comments.

Start making fs read(2) fail with EISDIR if the implementation does
not allow read on directories (kernfs, rumpfs, ptyfs and sysvbfs).
Adjust man page accordingly, and add a small corresponding vfs
testcase.

Slightly adjust skipped messages, makes output more consistent.

Add test for `ln -s / foo && cd foo'.

add ATF tests for v7fs. patch by njoly@. thank you.

Don't assume that "first lock that blocks" is a lock with the lowest
start offset and change the test to work when F_GETLK returns any
lock that blocks.

Even though msdosfs never truncates file names it advertises _PC_NO_TRUNC
as zero.  Make it advertise one (no_trunc == true).

Names longer than NAME_MAX (255) will never pass namei() btw.

Fixes PR #43670 (msdosfs claims support for filenames longer than {NAME_MAX},
                 but fails)

Remove "expected failure" for tmpfs PRs that are now fixed.

Make zero length symlinks work on tmpfs.

Fixes PR #43843 (tmpfs dies with kassert panic for 0 length symlink target)

Remove a vnode reference leak from msdosfs_rename. Release tdvp if either
doscheckpath() or relookup() fails.

Adjust test fs/vfs/t_vnops.c and remove the link count test for msdos.

Fixes PR #44661

Sync with HEAD

Apparently my last commit to msdosfs_vnops.c fixed the (harmless?)
buffer overrun in rename (>15 years old bug), so re-enable other
msdosfs rename tests too.

msdosfs xfail for PR kern/44661

xfail dir_rmdirdotdot for tmpfs (PR kern/44657)

Rmdir the dir you're in and its parent and try to cd ..
Fails on tmpfs (crash), puffs (cd .. succeeds) and rumpfs (cd .. succeeds).

another testcase derived from the bugfinding genious of Taylor R Campbell

Comment out msdosfs skip -- i'm not sure if it will still fail with
the "stack size" problem, but at least it fails due to yet another
refcounting snafu in the msdosfs rename method.

augment rename test case with the failure from PR kern/44288

Add simple test case for access(2), including panicky scenario from
PR kern/44648.

add some tests

Sync with HEAD

Add test case for F_GETLK pid-oddness from PR kern/44494.

I found the test case a little difficult to understand (because of
many indices), so I added a few more comments after I think I
figured out what was going on.

add test for kern/43321, blessed by pooka@

Check that file attributes can be changed (where applicable).

skip tests which use features which rumpfs does not support
(namely: vop_rename and a file system size limit)

s/dirs/symlinks/ in USES_SYMLINKS message.

fill in PR number: kern/43843

symlink to a zero-len target (and watch tmpfs go kabloom)

The erroneous error codes described in kern/43616 have been fixed.

Add create and rename testcases to exercize filenames longer than
{NAME_MAX}.

convert to newstyle automagic rump compat syscalls

Some of the msdosfs tests are killed by SSP due to stack limit
being exceeded.  I cannot figure out what is going on by code
reading, nor repeat this either on my desktop or in qemu, so skip
those tests for msdosfs until I can get to the bottom of it.

Add an assortment of rename tests.  Not complete, but at least tests
something.

This contains the tests for PR kern/43616 and PR kern/43617.

Add a few simple basic-level tests for vnodeops.  They don't cover
corner-cases, but make sure things at least superficially work
(which they always don't).  More to come...