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>] [day] [month] [year] [list]
Date:	Fri, 18 Dec 2009 10:51:14 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Joel Becker <Joel.Becker@...cle.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tao Ma <tao.ma@...cle.com>, Christoph Hellwig <hch@....de>
Subject: linux-next: manual merge of the ocfs2 tree with Linus' tree

Hi Joel,

Today's linux-next merge of the ocfs2 tree got a conflict in
fs/ocfs2/file.c between commit 6b2f3d1f769be5779b479c37800229d9a4809fc3
("vfs: Implement proper O_SYNC semantics") from Linus' tree and commit
a8227ccc585025735bcf350f71fa9c1ffd005d8d ("ocfs2: Handle O_DIRECT when
writing to a refcounted cluster") from the ocfs2 tree.

I fixed it up (see below) and can carry the fix for a while.  Since this
is a conflict against Linus' tree, it is fixable in the ocfs2 tree by
doing a merge with Linus' tree.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

diff --cc fs/ocfs2/file.c
index 3d30a1c,04e178e..0000000
--- a/fs/ocfs2/file.c
+++ b/fs/ocfs2/file.c
@@@ -2006,7 -2013,8 +2013,8 @@@ out_dio
  	/* buffered aio wouldn't have proper lock coverage today */
  	BUG_ON(ret == -EIOCBQUEUED && !(file->f_flags & O_DIRECT));
  
- 	if ((file->f_flags & O_DSYNC && !direct_io) || IS_SYNC(inode)) {
 -	if ((file->f_flags & O_SYNC && !direct_io) || IS_SYNC(inode) ||
++	if ((file->f_flags & O_DSYNC && !direct_io) || IS_SYNC(inode) ||
+ 	    (file->f_flags & O_DIRECT && has_refcount)) {
  		ret = filemap_fdatawrite_range(file->f_mapping, pos,
  					       pos + count - 1);
  		if (ret < 0)
--
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