From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Brauner <christian@brauner•io>
Cc: Miklos Szeredi <miklos@szeredi•hu>,
Christian Brauner <christian.brauner@ubuntu•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Miklos Szeredi <mszeredi@redhat•com>,
Tycho Andersen <tycho@tycho•pizza>
Subject: Re: linux-next: manual merge of the pidfd tree with the overlayfs tree
Date: Fri, 5 Feb 2021 09:40:26 +1100 [thread overview]
Message-ID: <20210205094026.1fa71254@canb.auug.org.au> (raw)
In-Reply-To: <20210125170716.4d6d83f3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Hi all,
On Mon, 25 Jan 2021 17:07:16 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the pidfd tree got a conflict in:
>
> fs/overlayfs/inode.c
>
> between commit:
>
> 9c09be9e71c4 ("ovl: perform vfs_getxattr() with mounter creds")
>
> from the overlayfs tree and commit:
>
> c7c7a1a18af4 ("xattr: handle idmapped mounts")
>
> from the pidfd 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/overlayfs/inode.c
> index cf41bcb664bc,e78d45dfeaee..000000000000
> --- a/fs/overlayfs/inode.c
> +++ b/fs/overlayfs/inode.c
> @@@ -352,9 -354,7 +354,9 @@@ int ovl_xattr_set(struct dentry *dentry
> goto out;
>
> if (!value && !upperdentry) {
> + old_cred = ovl_override_creds(dentry->d_sb);
> - err = vfs_getxattr(realdentry, name, NULL, 0);
> + err = vfs_getxattr(&init_user_ns, realdentry, name, NULL, 0);
> + revert_creds(old_cred);
> if (err < 0)
> goto out_drop_write;
> }
This is now a conflict between the pidfd tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-04 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 6:07 linux-next: manual merge of the pidfd tree with the overlayfs tree Stephen Rothwell
2021-02-04 22:40 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-25 6:04 Stephen Rothwell
2021-02-04 22:42 ` Stephen Rothwell
2021-01-25 5:23 Stephen Rothwell
2021-01-31 23:19 ` 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=20210205094026.1fa71254@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=christian.brauner@ubuntu$(echo .)com \
--cc=christian@brauner$(echo .)io \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miklos@szeredi$(echo .)hu \
--cc=mszeredi@redhat$(echo .)com \
--cc=tycho@tycho$(echo .)pizza \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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