From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <christian@brauner.io>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: manual merge of the pidfd tree with Linus' tree
Date: Tue, 9 Jul 2019 10:19:57 +1000 [thread overview]
Message-ID: <20190709101957.529cbb33@canb.auug.org.au> (raw)
In-Reply-To: <20190701203513.2ee7785b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
Hi all,
On Mon, 1 Jul 2019 20:35:13 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the pidfd tree got a conflict in:
>
> kernel/fork.c
>
> between commits:
>
> 9014143bab2f ("fork: don't check parent_tidptr with CLONE_PIDFD")
> 6fd2fe494b17 ("copy_process(): don't use ksys_close() on cleanups")
>
> from Linus' tree and commit:
>
> 7f192e3cd316 ("fork: add clone3")
>
> 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc kernel/fork.c
> index 947bc0161f9c,4114a044822c..000000000000
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@@ -1755,7 -1794,7 +1776,8 @@@ static __latent_entropy struct task_str
> int pidfd = -1, retval;
> struct task_struct *p;
> struct multiprocess_signals delayed;
> + struct file *pidfile = NULL;
> + u64 clone_flags = args->flags;
>
> /*
> * Don't allow sharing the root directory with processes in a different
> @@@ -2030,16 -2070,7 +2050,16 @@@
> goto bad_fork_free_pid;
>
> pidfd = retval;
> +
> + pidfile = anon_inode_getfile("[pidfd]", &pidfd_fops, pid,
> + O_RDWR | O_CLOEXEC);
> + if (IS_ERR(pidfile)) {
> + put_unused_fd(pidfd);
> + goto bad_fork_free_pid;
> + }
> + get_pid(pid); /* held by pidfile now */
> +
> - retval = put_user(pidfd, parent_tidptr);
> + retval = put_user(pidfd, args->pidfd);
> if (retval)
> goto bad_fork_put_pidfd;
> }
I am still getting this conflict (the commit ids may have changed).
Just a reminder in case you think Linus may need to know.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-09 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 10:35 linux-next: manual merge of the pidfd tree with Linus' tree Stephen Rothwell
2019-07-09 0:19 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-02 23:42 Stephen Rothwell
2023-07-03 7:50 ` Christian Brauner
2019-11-15 5:32 Stephen Rothwell
2019-07-04 8:44 Stephen Rothwell
2019-06-06 5:40 Stephen Rothwell
2019-06-06 5:40 ` Stephen Rothwell
2019-07-08 23:17 ` Stephen Rothwell
2019-05-22 1:01 Stephen Rothwell
2019-05-22 5:52 ` Greg Kroah-Hartman
2019-05-22 7:48 ` Stephen Rothwell
2019-05-22 7:55 ` Christian Brauner
2019-05-22 8:05 ` 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=20190709101957.529cbb33@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christian@brauner.io \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).