[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11446.1401420931@jrobl>
Date: Fri, 30 May 2014 12:35:31 +0900
From: "J. R. Okajima" <hooanon05g@...il.com>
To: David Howells <dhowells@...hat.com>
Cc: Miklos Szeredi <miklos@...redi.hu>, viro@...IV.linux.org.uk,
torvalds@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, hch@...radead.org,
akpm@...ux-foundation.org, apw@...onical.com, nbd@...nwrt.org,
neilb@...e.de, jordipujolp@...il.com, ezk@....cs.sunysb.edu,
sedat.dilek@...il.com, mszeredi@...e.cz
Subject: Re: Unionmount and overlayfs testsuite
David Howells:
> http://git.infradead.org/users/dhowells/unionmount-testsuite.git
I've found some interesting cases.
- impermissible.test,
open_file_as_bin -t -w $file -E EACCES
When $termslash is "/", a '/' is appended to the expanded $file, such
as "/path/fileA/". If fileA is a regular file, that path is obviously
wrong. Does UnionMount expect EACCES in this case too?
Should it be ENOTDIR?
It might be better to change
errcode=EACCES
test ! "$termslash" = "" && errcode=ENOTDIR
open_file_as_bin -t -w $file -E $errcode
- readlink.test,
fs_op readlink $file -R $testdir/direct_dir_sym100 ${termslash:+-E EINVAL}
It expects "$testdir/direct_dir_sym100". Does it mean UnionMount
converts the target path?
For example,
- /u = /rw + /ro
- /rw/symlinkA doesn't exist
- /ro/symlinkA points to /ro/fileA
Does readlink(2) return "/u/fileA" instead of "/u/fileA"?
And all tests should be done by a superuser?
J. R. Okajima
--
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/
Powered by blists - more mailing lists