linux-kernel - linux-next: manual merge of the ext3 tree with the cifs tree

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: <20091125140626.2b71fb0a.sfr@canb.auug.org.au>
Date:	Wed, 25 Nov 2009 14:06:26 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@....de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Steve French <sfrench@...ibm.com>,
	Jeff Layton <jlayton@...hat.com>
Subject: linux-next: manual merge of the ext3 tree with the cifs tree

Hi Jan,

Today's linux-next merge of the ext3 tree got a conflict in fs/cifs/dir.c
between commit cea62343956c24452700c06cf028b72414c58a74 ("[CIFS]
Duplicate data on appending to some Samba servers") from the cifs tree
and commit 618903228b94b67a1d04634a83ea9cdb99c09e37 ("vfs: Implement
proper O_SYNC semantics") from the ext3 tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

diff --cc fs/cifs/dir.c
index 1f42f77,f1fe5cb..0000000
--- a/fs/cifs/dir.c
+++ b/fs/cifs/dir.c
@@@ -214,7 -214,10 +214,8 @@@ int cifs_posix_open(char *full_path, st
  		posix_flags |= SMB_O_EXCL;
  	if (oflags & O_TRUNC)
  		posix_flags |= SMB_O_TRUNC;
- 	if (oflags & O_SYNC)
 -	if (oflags & O_APPEND)
 -		posix_flags |= SMB_O_APPEND;
+ 	/* be safe and imply O_SYNC for O_DSYNC */
+ 	if (oflags & O_DSYNC)
  		posix_flags |= SMB_O_SYNC;
  	if (oflags & O_DIRECTORY)
  		posix_flags |= SMB_O_DIRECTORY;
--
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/