linux-ext4 - [PATCH 0/2] ext3 in-inode xattr handling fix for reserved inodes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1284467566-12661-1-git-send-email-jack@suse.cz>
Date:	Tue, 14 Sep 2010 14:32:44 +0200
From:	Jan Kara <jack@...e.cz>
To:	linux-ext4@...r.kernel.org
Cc:	Andreas Dilger <adilger.kernel@...ger.ca>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/2] ext3 in-inode xattr handling fix for reserved inodes

  Hi,

  the first patch in this series fixes a bug where we could lose extended
attributes for ino 11 if lost+found was deleted and inode used again.
The second patch makes kernel accept in-inode xattrs even for reserved
inodes if they look sane as Andreas suggested. This way we could in theory
remove the special casing sometime in future. I'm personally not convinced
this is worth the effort since the time when we could remove the special
casing is at least several years in future (for example I switch to 2.6.16
or even older kernels on our test machines) but I'm throwing the patch
in so that people can express their opinions...

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