linux-kernel - Re: 2.6.29 -mm merge plans

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: <Pine.LNX.4.64.0901081255580.17013@localhost.localdomain>
Date:	Mon, 12 Jan 2009 04:19:57 +0100 (CET)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Warren Turkal <wt@...guintechs.org>
cc:	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Diego Elio 'Flameeyes' Petten?" <flameeyes@...il.com>
Subject: Re: 2.6.29 -mm merge plans

Hi,

On Tue, 6 Jan 2009, Warren Turkal wrote:

(Sorry for the delay.)

> I have a drive at home with the condition. So empirically, it can happen.

One problem is that there is no explanation how it happened.
The other problem is that in the Apple driver or tools I haven't found an 
equivalent (unless you disable journaling completely), there is simply no 
special handling of a zero in this field.
I find it more likely that some repair tool simply sets this field to 
zero, so it forces the OS X driver to reinitialize the journal file. It 
might help to look at the last_mount field to have some idea who accessed 
the volume last.
So your first patch is kinda trivial, although most of comment isn't 
needed and is irrelevant to the patch itself, however I don't see a reason
to apply the second patch.

bye, Roman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/