linux-ext4 - Re: Updated ext4 quota design document

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:	Wed, 23 Jun 2010 14:30:14 +0200
From:	Jan Kara <jack@...e.cz>
To:	tytso@....edu
Cc:	Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org
Subject: Re: Updated ext4 quota design document

On Tue 22-06-10 17:52:00, tytso@....edu wrote:
> On Tue, Jun 22, 2010 at 10:29:27PM +0200, Jan Kara wrote:
> >   With metadata which get journaled it should be quite easy. JBD already
> > must know before you go and modify buffer contents - that's why
> > journal_get_write_access and friends exist. It also makes sure that your
> > data cannot be modified from the moment the buffer enters commit upto the
> > moment the commit is finished. So you can use buffer commit hook to compute
> > and store block checksum safely.
> 
> True, but we're also interested in making sure this feature can be
> used in the non-journal case as well....
  Ah, I forgot about that... Doing per-block checksums in that case would
be indeed more complicated. So computing checksum for each dquot is
probably simpler.

								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