From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
Bob Peterson <rpeterso@redhat.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the gfs2 tree with the btrfs tree
Date: Mon, 16 May 2022 12:12:32 +1000 [thread overview]
Message-ID: <20220516121232.6cf7660b@canb.auug.org.au> (raw)
In-Reply-To: <20220510102458.0ab0172f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
Hi all,
On Tue, 10 May 2022 10:24:58 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the gfs2 tree got a conflict in:
>
> fs/gfs2/file.c
>
> between commit:
>
> 39c93b0bf7a6 ("iomap: add per-iomap_iter private data")
>
> from the btrfs tree and commit:
>
> db0c1968e935 ("gfs2: Variable rename")
>
> from the gfs2 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.
>
>
> diff --cc fs/gfs2/file.c
> index 76307a90bf81,d18a7c2201c0..000000000000
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@@ -839,11 -839,12 +839,12 @@@ retry_under_glock
> pagefault_disable();
> to->nofault = true;
> ret = iomap_dio_rw(iocb, to, &gfs2_iomap_ops, NULL,
> - IOMAP_DIO_PARTIAL, NULL, written);
> - IOMAP_DIO_PARTIAL, read);
> ++ IOMAP_DIO_PARTIAL, NULL, read);
> to->nofault = false;
> pagefault_enable();
> + /* No increment (+=) because iomap_dio_rw returns a cumulative value. */
> if (ret > 0)
> - written = ret;
> + read = ret;
>
> if (should_fault_in_pages(ret, to, &prev_count, &window_size)) {
> size_t leftover;
> @@@ -906,7 -908,7 +908,7 @@@ retry_under_glock
>
> from->nofault = true;
> ret = iomap_dio_rw(iocb, from, &gfs2_iomap_ops, NULL,
> - IOMAP_DIO_PARTIAL, NULL, read);
> - IOMAP_DIO_PARTIAL, written);
> ++ IOMAP_DIO_PARTIAL, NULL, written);
> from->nofault = false;
>
> if (ret == -ENOTBLK)
This is now a conflict between the btrfs tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-16 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 0:24 Stephen Rothwell
2022-05-16 2:12 ` Stephen Rothwell [this message]
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=20220516121232.6cf7660b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agruenba@redhat.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=swhiteho@redhat.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
all inboxes | Powered by JetHome®