public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Documentation on Replacement of Deprecated O_SYNC_* FS flags/calls
Date: Tue, 24 Aug 2010 11:59:35 +0100	[thread overview]
Message-ID: <4C73A617.7010201@bobich.net> (raw)

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

                 reply	other threads:[~2010-08-24 11:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C73A617.7010201@bobich.net \
    --to=gordan@bobich.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox