All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Omar Sandoval <osandov@fb.com>,
	Nikolay Borisov <nborisov@suse.com>, Chris Mason <clm@fb.com>
Subject: Re: linux-next: manual merge of the btrfs-kdave tree with Linus' tree
Date: Mon, 4 Sep 2017 16:02:30 +1000	[thread overview]
Message-ID: <20170904160230.3912011f@canb.auug.org.au> (raw)
In-Reply-To: <20170825095825.60c576f3@canb.auug.org.au>

Hi all,

On Fri, 25 Aug 2017 09:58:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the btrfs-kdave tree got a conflict in:
> 
>   fs/btrfs/inode.c
> 
> between commit:
> 
>   58efbc9f5463 ("Btrfs: fix blk_status_t/errno confusion")
> 
> from Linus' tree and commit:
> 
>   e6961cac730f ("btrfs: Move skip checksum check from btrfs_submit_direct to __btrfs_submit_dio_bio")
> 
> from the btrfs-kdave 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/btrfs/inode.c
> index 24bcd5cd9cf2,d184a46e46c4..000000000000
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@@ -7991,10 -8080,9 +8081,10 @@@ static blk_status_t dio_read_error(stru
>   	struct extent_io_tree *failure_tree = &BTRFS_I(inode)->io_failure_tree;
>   	struct bio *bio;
>   	int isector;
> - 	int read_mode = 0;
> + 	unsigned int read_mode = 0;
>   	int segs;
>   	int ret;
>  +	blk_status_t status;
>   
>   	BUG_ON(bio_op(failed_bio) == REQ_OP_WRITE);
>   
> @@@ -8021,11 -8109,11 +8111,11 @@@
>   	bio_set_op_attrs(bio, REQ_OP_READ, read_mode);
>   
>   	btrfs_debug(BTRFS_I(inode)->root->fs_info,
> - 		    "Repair DIO Read Error: submitting new dio read[%#x] to this_mirror=%d, in_validation=%d\n",
> + 		    "repair DIO read error: submitting new dio read[%#x] to this_mirror=%d, in_validation=%d",
>   		    read_mode, failrec->this_mirror, failrec->in_validation);
>   
>  -	ret = submit_dio_repair_bio(inode, bio, failrec->this_mirror);
>  -	if (ret) {
>  +	status = submit_dio_repair_bio(inode, bio, failrec->this_mirror);
>  +	if (status) {
>   		free_io_failure(failure_tree, io_tree, failrec);
>   		bio_put(bio);
>   	}
> @@@ -8426,9 -8513,8 +8516,9 @@@ static inline blk_status_t btrfs_lookup
>   	return 0;
>   }
>   
>  -static inline int __btrfs_submit_dio_bio(struct bio *bio, struct inode *inode,
>  -					 u64 file_offset, int async_submit)
>  +static inline blk_status_t
>  +__btrfs_submit_dio_bio(struct bio *bio, struct inode *inode, u64 file_offset,
> - 		       int skip_sum, int async_submit)
> ++		       int async_submit)
>   {
>   	struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
>   	struct btrfs_dio_private *dip = bio->bi_private;
> @@@ -8541,9 -8625,9 +8630,9 @@@ static int btrfs_submit_direct_hook(str
>   		 */
>   		atomic_inc(&dip->pending_bios);
>   
> - 		status = __btrfs_submit_dio_bio(bio, inode, file_offset, skip_sum,
>  -		ret = __btrfs_submit_dio_bio(bio, inode, file_offset,
>  -					     async_submit);
>  -		if (ret) {
> ++		status = __btrfs_submit_dio_bio(bio, inode, file_offset,
>  +						async_submit);
>  +		if (status) {
>   			bio_put(bio);
>   			atomic_dec(&dip->pending_bios);
>   			goto out_err;
> @@@ -8561,9 -8645,8 +8650,8 @@@
>   	} while (submit_len > 0);
>   
>   submit:
> - 	status = __btrfs_submit_dio_bio(bio, inode, file_offset, skip_sum,
> - 					async_submit);
>  -	ret = __btrfs_submit_dio_bio(bio, inode, file_offset, async_submit);
>  -	if (!ret)
> ++	status = __btrfs_submit_dio_bio(bio, inode, file_offset, async_submit);
>  +	if (!status)
>   		return 0;
>   
>   	bio_put(bio);

Just a reminder that this conflict still exists.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-09-04  6:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 23:58 linux-next: manual merge of the btrfs-kdave tree with Linus' tree Stephen Rothwell
2017-09-04  6:02 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-19 11:31 Mark Brown
2019-09-23 11:59 ` David Sterba
2018-02-06 23:49 Stephen Rothwell
2018-02-06 23:45 Stephen Rothwell
2017-07-24  0:54 Stephen Rothwell
2017-07-18  0:18 Stephen Rothwell
2017-07-21 13:49 ` David Sterba
2016-12-14 23:25 Stephen Rothwell
2016-09-05  1:47 Stephen Rothwell
2016-04-05  0:32 Stephen Rothwell
2016-04-05  0:32 Stephen Rothwell
2016-04-05  0:32 Stephen Rothwell
2016-02-01 23:22 Stephen Rothwell
2016-02-02  5:16 ` Chandan Rajendra

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=20170904160230.3912011f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=osandov@fb.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 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.