From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Whitehouse <swhiteho@redhat.com>,
Bob Peterson <rpeterso@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Andreas Gruenbacher <agruenba@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the gfs2 tree with the vfs tree
Date: Wed, 9 Jun 2021 12:13:49 +1000 [thread overview]
Message-ID: <20210609121349.74ba0b69@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
Hi all,
Today's linux-next merge of the gfs2 tree got conflicts in:
include/linux/uio.h
lib/iov_iter.c
between commit:
c8129a6f6ed1 ("sanitize iov_iter_fault_in_readable()")
from the vfs tree and commit:
f8524fce6a88 ("iov_iter: Add iov_iter_fault_in_writeable()")
from the gfs2 tree.
I fixed it up (see below - both commits fixed up the indentation in
iov_iter_fault_in_readable()) 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 include/linux/uio.h
index fd88d9911dad,6811eb6ac6e3..000000000000
--- a/include/linux/uio.h
+++ b/include/linux/uio.h
@@@ -115,11 -119,12 +115,12 @@@ static inline struct iovec iov_iter_iov
};
}
-size_t iov_iter_copy_from_user_atomic(struct page *page,
- struct iov_iter *i, unsigned long offset, size_t bytes);
+size_t copy_page_from_iter_atomic(struct page *page, unsigned offset,
+ size_t bytes, struct iov_iter *i);
void iov_iter_advance(struct iov_iter *i, size_t bytes);
void iov_iter_revert(struct iov_iter *i, size_t bytes);
-int iov_iter_fault_in_readable(struct iov_iter *i, size_t bytes);
+int iov_iter_fault_in_readable(const struct iov_iter *i, size_t bytes);
+ int iov_iter_fault_in_writeable(struct iov_iter *i, size_t bytes);
size_t iov_iter_single_seg_count(const struct iov_iter *i);
size_t copy_page_to_iter(struct page *page, size_t offset, size_t bytes,
struct iov_iter *i);
diff --cc lib/iov_iter.c
index 8842ca6995c3,317c94eac907..000000000000
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-09 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 2:13 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-11 1:12 linux-next: manual merge of the gfs2 tree with the vfs tree Stephen Rothwell
2021-06-11 1:46 ` Al Viro
2021-06-11 14:45 ` Andreas Gruenbacher
2021-06-22 1:38 ` Stephen Rothwell
2021-06-22 6:48 ` Andreas Gruenbacher
2021-06-22 21:56 ` Stephen Rothwell
2019-07-08 3:48 Stephen Rothwell
2019-07-12 0:56 ` Stephen Rothwell
2010-01-27 0:17 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=20210609121349.74ba0b69@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agruenba@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=swhiteho@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox