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>] [day] [month] [year] [list]
Message-ID: <4C73A617.7010201@bobich.net>
Date:	Tue, 24 Aug 2010 11:59:35 +0100
From:	Gordan Bobic <gordan@...ich.net>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Documentation on Replacement of Deprecated O_SYNC_* FS flags/calls

Hi,

I'm trying to port e2compr patches to 2.6.35.2, and I've run into the 
following issue. The code here, that I need to patch into fs/ext2/file.c:

=============
if (status >= 0) {
	if ((file->f_flags & O_SYNC) || IS_SYNC(inode)) {
		if (ei->i_compr_flags & EXT2_OSYNC_INODE) {
			osync_already = 1;
		} else {
			osync_already = 0;
			ei->i_compr_flags |= EXT2_OSYNC_INODE;
		}

		/* Should 2nd arg be inode->i_mapping? */
		status = generic_osync_inode(inode, file->f_mapping,
			OSYNC_METADATA|OSYNC_DATA);
		if (osync_already == 0) {
			ei->i_compr_flags &= ~EXT2_OSYNC_INODE;
		}
	}
}
=============

uses the deprecated O_SYNC_* flags that have been deprecated and removed 
around the 2.6.31 era. Is there any documentation available on the new 
way this should be done?

Many thanks.

Gordan
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ