From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>, Jeff Layton <jlayton@poochiereds.net>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: linux-next: manual merge of the block tree with the file-locks tree
Date: Wed, 21 Jun 2017 13:17:36 +1000 [thread overview]
Message-ID: <20170621131736.44dc39ac@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the block tree got a conflict in:
fs/ext4/file.c
between commit:
c37683e32cca ("ext4: add more robust reporting of metadata writeback errors")
from the file-locks tree and commit:
728fbc0e10b7 ("ext4: nowait aio support")
from the block tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc fs/ext4/file.c
index d41d3d0b4ef1,58e2eeaa0bc4..000000000000
--- a/fs/ext4/file.c
+++ b/fs/ext4/file.c
@@@ -435,13 -454,11 +454,17 @@@ static int ext4_file_open(struct inode
if (ret < 0)
return ret;
}
+
+ /* Set the flags to support nowait AIO */
+ filp->f_mode |= FMODE_AIO_NOWAIT;
+
- return dquot_file_open(inode, filp);
+ ret = dquot_file_open(inode, filp);
+ if (!ret) {
+ struct inode *bd_inode = sb->s_bdev->bd_inode;
+
+ filp->f_md_wb_err = filemap_sample_wb_err(bd_inode->i_mapping);
+ }
+ return ret;
}
/*
next reply other threads:[~2017-06-21 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 3:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 1:57 linux-next: manual merge of the block tree with the file-locks tree Stephen Rothwell
2017-06-28 2:01 ` Jens Axboe
2017-06-28 9:54 ` Jeff Layton
2017-06-28 12:44 ` Jens Axboe
2017-06-21 2:48 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=20170621131736.44dc39ac@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=axboe@kernel.dk \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rgoldwyn@suse.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