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: <20110629044955.GA30312@untroubled.org>
Date:	Tue, 28 Jun 2011 22:49:55 -0600
From:	Bruce Guenter <bruce@...roubled.org>
To:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH v2] ext4: Deprecate data=journal mount option

On Tue, Jun 28, 2011 at 01:26:03PM +0200, Lukas Czerner wrote:
> Data journalling mode (data=journal) is known to be neglected by
> developers and only minority of people is actually using it. This
> mode is also less tested than the other two modes by the developers.
> 
> This creates a dangerous combination, because the option which seems
> *safer* is actually less safe the others. So this commit adds a warning
> message in case that data=journal mode is used, so the user is informed
> that the mode might be removed in the future.

When I last benchmarked it, data=journal mode was considerably faster
than the other modes for sync heavy work loads, such as mail servers.
Have there been improvements to other (safe) modes that reverse this?

-- 
Bruce Guenter <bruce@...roubled.org>                http://untroubled.org/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ