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: <20100326105733.GC3055@quack.suse.cz>
Date:	Fri, 26 Mar 2010 11:57:33 +0100
From:	Jan Kara <jack@...e.cz>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	Andreas Dilger <andreas.dilger@...cle.com>, tytso@....edu,
	Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH,RFC] Adding quotacheck functionality to e2fsck

On Fri 26-03-10 11:18:28, Dmitry Monakhov wrote:
> > If there isn't a reason to continue using unjournaled quota (i.e. it
> > doesn't break to just move to journaled quota everywhere), then these
> > could just become aliases for the journaled quota implementation.  The
> > other alternative is to deprecate these options in the next kernel and
> > have it print out a warning on the console to tell the user to switch
> > over to the journaled version.
> The only reason to not use journalled quota by default is the currently
> it is a bit slower than unjournalled variant.
> This is because each quota change result in synchronous quotafile 
> update in per-sb-page-cache. And this update is protected by i_mutex.
> and dqio_mutex. It may be fixed easily. I've sent a RFC patch two
> month ago. I'll update it and will submit it this weekend. 
  Well, there is also some overhead caused by more IO we have to do for
quota journaling and that is essentially unavoidable. But still I believe
we should transition people to journaled quotas...

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ