[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20210412120313.20efd984@canb.auug.org.au>
Date: Mon, 12 Apr 2021 12:03:13 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Al Viro <viro@...IV.linux.org.uk>,
Miklos Szeredi <miklos@...redi.hu>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Miklos Szeredi <mszeredi@...hat.com>,
Sargun Dhillon <sargun@...gun.me>
Subject: linux-next: manual merge of the vfs tree with the overlayfs tree
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/overlayfs/file.c
between commit:
d46b7cd68336 ("ovl: plumb through flush method")
from the overlayfs tree and commit:
ae7db6c8bc98 ("ovl: remove unneeded ioctls")
from the vfs 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/overlayfs/file.c
index 6e454a294046,9bd4167cc7fb..000000000000
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@@ -716,11 -590,6 +610,7 @@@ const struct file_operations ovl_file_o
.mmap = ovl_mmap,
.fallocate = ovl_fallocate,
.fadvise = ovl_fadvise,
- .unlocked_ioctl = ovl_ioctl,
+ .flush = ovl_flush,
- #ifdef CONFIG_COMPAT
- .compat_ioctl = ovl_compat_ioctl,
- #endif
.splice_read = generic_file_splice_read,
.splice_write = iter_file_splice_write,
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists