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  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]
Date:	Fri, 12 Aug 2011 16:57:19 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Ted Ts'o <tytso@....edu>
Cc:	Lukas Czerner <lczerner@...hat.com>,
	Curt Wohlgemuth <curtw@...gle.com>,
	Ric Wheeler <rwheeler@...hat.com>,
	Andreas Dilger <adilger@...ger.ca>,
	linux-ext4 List <linux-ext4@...r.kernel.org>,
	Jan Kara <jack@...e.cz>, Eric Sandeen <sandeen@...hat.com>
Subject: Re: [PATCH v2] ext4: Deprecate data=journal mount option

On Fri, Aug 12, 2011 at 02:13:30PM -0400, Ted Ts'o wrote:
> I have a rather long list of expected failures, mostly having to do
> with xfstests assuming that O_DIRECT has to be supported.  On my todo
> list is to scrub through the list failures that I've seen, make sure
> they are indeed related to O_DIRECT, and then see if I can figure out
> some way of telling xfstests to skip O_DIRECT tests via some
> environment variable or command line option.

If you do it please do it by returning a defined failure from the
test programs and then just exiting the test with _notrun.  But given
that xfstests does a lot of O_DIRECT testing it might be quite involved.

To be honest I'd expect a Linux filesystem without O_DIRECT not working
overly well in practical setup - it's pretty widely used these days.
A better fix might be simply accept O_DIRECT for data=journal, but
use the pagecache with a use once hint.

> BTW, with the very latest xfstests, I'm seeing new across-the-board
> (not just data=journal) failures for tests #62 (caused by the presence
> of the lost+found directory

062 fails because Andreas changed the error returns from the xattr
calls.  He sent me a patch to accept the new errors, but I'm still
undecided wether the new ones are correct enough.  I'll wait another
kernel release to see if real users complain about the change, and
will apply it then.

> and differences in error code returns for
> xattrs) and #79 (a failure in the append-only handling which I don't
> completely understand yet).

This was discussed on fsdevel lately.  All filesystem but xfs inherit
the append only bit from directories to files created inside them.
This not only is not very useful behaviour, but also exposes a bug
in the vfs that allows to create these new files, but fail the open
unless using O_APPEND which is against the posix create semantics.

We'll have to either adopt the oether filesystems to the xfs semantics,
or adopt xfs to the common dumb semantics and fix that O_CREAT bug.

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

Powered by blists - more mailing lists