linux-ext4 - [PATCH 0/6] inode version updated patches

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-next>] [day] [month] [year] [list]

Message-Id: <1181836571.7779.42.camel@garfield>
Date:	Thu, 14 Jun 2007 21:26:11 +0530
From:	Kalpak Shah <kalpak@...sterfs.com>
To:	linux-ext4 <linux-ext4@...r.kernel.org>
Cc:	Andreas Dilger <adilger@...sterfs.com>,
	Jean noel Cordenner <jean-noel.cordenner@...l.net>
Subject: [PATCH 0/6] inode version updated patches

Hi,

I have updated the inode version patches and below are the details:

64-bit-i_version.patch which only replaces the 32-bit i_version field in
the generic inode with a 64-bit i_version field. The VFS-level updates
of the inode version are still in the i_version_update_vfs.patch and
this patch has been moved to the bottom of the patch series.

ext4_i_version_hi_2.patch was still using ei->i_fs_version instead of
inode->i_version. I have corrected this patch.

Also there were whitespace problems in i_version_hi.patch.

I am also attaching a ext4_no_version.patch which adds a "noversion"
mount option to disable inode version updates.

I am not sure why i_version needs to be updated in VFS since it is being
updated in ext4_mark_iloc_dirty().

Well, these are lots of small patches and I am sending them separately
so that they can be applied and commented upon easily.

Thanks,
Kalpak.

-
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