All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: manual merge of the vfs tree with the f2fs tree
Date: Tue, 10 Jun 2014 11:23:04 +1000	[thread overview]
Message-ID: <20140610112304.5ef43a2a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

Hi Al,

Today's linux-next merge of the vfs tree got a conflict in
fs/f2fs/data.c between commit b6fe5873cb42 ("f2fs: fix to recover data
written by dio") from the f2fs tree and commits d8d3d94b80aa ("pass
iov_iter to ->direct_IO()") and 31b140398ce5 ("switch
{__,}blockdev_direct_IO() to iov_iter") from the vfs tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

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

diff --cc fs/f2fs/data.c
index c1fb6dd10911,1d2e7e9624d2..000000000000
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@@ -1044,14 -1018,11 +1043,14 @@@ static ssize_t f2fs_direct_IO(int rw, s
  	if (f2fs_has_inline_data(inode))
  		return 0;
  
- 	if (check_direct_IO(inode, rw, iov, offset, nr_segs))
+ 	if (check_direct_IO(inode, rw, iter, offset))
  		return 0;
  
 +	/* clear fsync mark to recover these blocks */
 +	fsync_mark_clear(F2FS_SB(inode->i_sb), inode->i_ino);
 +
- 	return blockdev_direct_IO(rw, iocb, inode, iov, offset, nr_segs,
- 							get_data_block);
+ 	return blockdev_direct_IO(rw, iocb, inode, iter, offset,
+ 				  get_data_block);
  }
  
  static void f2fs_invalidate_data_page(struct page *page, unsigned int offset,

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2014-06-10  1:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  1:23 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 23:47 linux-next: manual merge of the vfs tree with the f2fs tree Stephen Rothwell
2023-12-20  0:13 ` Stephen Rothwell
2023-12-20  1:34   ` Al Viro
2023-12-20  3:05     ` Stephen Rothwell
2023-12-20  4:44       ` Al Viro
2021-04-19  0:53 Stephen Rothwell
2018-10-03  0:12 Stephen Rothwell
2017-11-08 23:06 Stephen Rothwell
2017-11-08 23:01 Stephen Rothwell
2017-02-27  0:05 Stephen Rothwell
2017-02-27  8:27 ` David Howells
2016-07-25  0:21 Stephen Rothwell
2016-05-03  1:41 Stephen Rothwell
2015-05-07  2:05 Stephen Rothwell
2015-04-13  1:53 Stephen Rothwell
2014-04-29  0:37 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=20140610112304.5ef43a2a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.