linux-ext4 - Re: [PATCH] [RFC] jbd2: Add buffer triggers

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:	Mon, 6 Oct 2008 14:37:55 -0700
From:	Joel Becker <Joel.Becker@...cle.com>
To:	Theodore Tso <tytso@....edu>
Cc:	ocfs2-devel@....oracle.com, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] [RFC] jbd2: Add buffer triggers

On Fri, Oct 03, 2008 at 08:03:36PM -0400, Theodore Tso wrote:
> I'm not sure you saw this e-mail, since I think it got in a mailman
> moderation queue.

	I've flagged you as "do not moderate".  I saw the email, but I
was in Prague for the cluster summit and didn't have time to look
in-depth.

> I've been looking more closely at this, and I think actually using
> this commit trigger gets very tricky.  Exactly how do you plan to use
> the commit trigger?  The caller is only going to be able to easily
> check the checksum on the frozen copy of the buffer; is that what you
> intended?  When and how do you plan set the checksum for a filesystem
> which is cleanly unmounted?  And are you planning on doing this for
> just the superblock, or for other data structures?  

	Every single metadata block in ocfs2 would have the commit
trigger set.  I intend to calculate the block checksums in the trigger.
That way I only compute the checksum once per journal write, rather than
every time I call journal_dirty_metadata().  That's my plan, at least.
	You may be right that my choice is too late and that I need to
trigger in an earlier place.  That's why I was taking time to reply: I
wanted to re-read the jbd2 source and be sure of what you were saying
and how I was handling it.  I haven't looked yet (just got back to the
office today), but here's what I understand so far.
	As far I could tell, actual writes of the buffer to the journal
go through journal_write_metadata_buffer().  Only in
journal_write_metadata_buffer() are you sure to have a frozen copy of
the buffer that won't be affected by parallel processes doing
journal_dirty_metadata().  Thus, the new_page and new_offset values are
set to b_data or b_frozen_data as needed.  When I get past that, I have
the right pointer.  I need to do it before the escape, of course,
because I want to checksum the block data, not the escaped data.
	Now, I'm sure this is the buffer that's going to the journal, I
think you're saying that this buffer may not be what gets checkpointed.
So the correct checksum hits the journal, but then an invalid one gets
to the real location on disk.  Is that right?  If so, I need to figure
out where to calculate the checksum somewhere higher, as you say.

Joel

-- 

"Nobody loves me,
 Nobody seems to care.
 Troubles and worries, people,
 You know I've had my share."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@...cle.com
Phone: (650) 506-8127
--
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