From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Steve French <sfrench@us.ibm.com>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: linux-next: manual merge of the ext3 tree with the cifs tree
Date: Wed, 25 Nov 2009 09:50:06 +0100 [thread overview]
Message-ID: <20091125085006.GB549@quack.suse.cz> (raw)
In-Reply-To: <20091125140626.2b71fb0a.sfr@canb.auug.org.au>
Hi,
On Wed 25-11-09 14:06:26, Stephen Rothwell wrote:
> 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.
Thanks for notification and fixup.
> Just context changes. I fixed it up (see below) and can carry the fix as
> necessary.
Looking at the code, I don't see an easy way of resolving this by changing
either mine or CIFS tree - I have other patches depending on this and this
patch depending on others and I assume it's similar with CIFS... So I guess
we'll have to live with this conflict.
Honza
> 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;
next prev parent reply other threads:[~2009-11-25 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 3:06 linux-next: manual merge of the ext3 tree with the cifs tree Stephen Rothwell
2009-11-25 8:50 ` Jan Kara [this message]
2009-11-25 9:04 ` Stephen Rothwell
2009-11-25 15:23 ` Eric Paris
-- strict thread matches above, loose matches on Subject: below --
2010-05-12 0:13 Stephen Rothwell
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=20091125085006.GB549@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sfrench@us.ibm.com \
/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