linux-ext4 - Re: [PATCH v2] ext4: Deprecate data=journal mount option

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]

Date:	Fri, 12 Aug 2011 14:13:30 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	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 06:08:21PM +0200, Lukas Czerner wrote:
> On Fri, 12 Aug 2011, Curt Wohlgemuth wrote:
> 
> > I don't know much about data=journal, but I've been running xfstests
> > with it, and it's a disaster, given that data=journal doesn't support
> > O_DIRECT.  What kind of testing do people do on data=journal?

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.

For the record this is what I mostly expect (from a somewhat older
xfstests) in the data=journal case:

Ran: 001 002 005 006 007 011 013 014 053 069 070 074 075 076 077 088 089 100 105 112 113 123 124 125 126 127 128 129 130 131 132 133 135 141 169 184 193 198 204 207 208 209 210 211 212 213 214 215 219 221 223 224 225 226 228 230 231 232 233 234 235 236 237 239 240 243 245 246 247 248 249 256
Failures: 113 125 130 133 135 198 207 208 209 210 214 223 226 239 240 245

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

> Short answer is probably none :). Even though that it seems like an
> radical answer I believe that it is mostly true, because simply said
> almost no-one care. But I think that Ted mentioned that he actually do
> some tests with that mode, but I am not sure about that.

Yes, I'm testing with data=journal, and I haven't been able to
reproduce the crash which curtw is seeing (see above; test #74 passes
in my 2cpu/512mb KVM test environment).  I'll add some instrumentation
to the BUG_ON in question and then try to reproduce it in curtw's
environment.

							- Ted
--
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