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:	Sat, 21 Oct 2006 21:09:50 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andrés G. Aragoneses [ knocte ] 
	<knocte@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Discussion about a "dirty bit" in the filesystem

On Sat, Oct 21, 2006 at 09:39:02PM +0200, "Andrés G. Aragoneses [ knocte ]" wrote:
> Hello. Sorry if this is not the correct place to talk about this.
> 
> I am writing to this list because I am a user of openSUSE that opened
> filed a bug [1] against the issue tracking software of this linux
> distribution about boot management and hibernation. There was a
> discussion and then the bug was resolved to WONTFIX, but I think we
> could extract from it a nice FEATURE that any filesystem would have, or,
> in particular, ext4.
> 
> [1] https://bugzilla.novell.com/show_bug.cgi?id=175939
> 
> Any opinions?

I'm not at all sure what this has to do with ext4 at all.  The last
message indicates a major problem with your request, which is that if
a FAT partition is mounted by Linux, and in the middle of being
modified when the system is undergoing hibernation, and then Windows
is booted and modifies the filesystem, you can lose data.  But that's
because the FAT filesystem can be understood by both Windows and
Linux.  (Presumably this problem would also occur, in a much worse
case, using NTFS.)  But this has nothing to do with ext4.

I can imagine someone writing an improved hibernate script which
checks to see if a filesystem which could be understood by Windows
(i.e., FAT or NTFS) is mounted, and if any such filesystems are
mounted, disable the ability to boot into Windows after the
hibernation.  I could even imagine an improved hibernate script which
detects this case, and attempts to unmount the FAT and NTFS
filesystems, and if it could successfully unmount them all, allow the
user to reboot into Windows after hibernation.

However, this is not a ext4 filesystem matter, and not a kernel
matter, but rather a hibernation script issue.

Regards,

						- Ted
-
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