From: Stephen Rothwell <[email protected]>
To: "Eric W. Biederman" <[email protected]>,
Thomas Gleixner <[email protected]>,
Ingo Molnar <[email protected]>, "H. Peter Anvin" <[email protected]>,
Peter Zijlstra <[email protected]>
Cc: Borislav Petkov <[email protected]>, Brian Gerst <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
Linux Next Mailing List <[email protected]>
Subject: linux-next: manual merge of the userns tree with the tip tree
Date: Mon, 9 May 2022 16:49:37 +1000 [thread overview]
Message-ID: <[email protected]> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hi all,
Today's linux-next merge of the userns tree got a conflict in:
arch/x86/kernel/process.c
between commit:
3a24a60854d2 ("x86/32: Remove lazy GS macros")
from the tip tree and commit:
5bd2e97c868a ("fork: Generalize PF_IO_WORKER handling")
from the userns 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 arch/x86/kernel/process.c
index 4037aaaf0260,d20eaad52a85..000000000000
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@@ -193,10 -193,14 +195,10 @@@ int copy_thread(struct task_struct *p,
if (sp)
childregs->sp = sp;
- if (unlikely(p->flags & PF_IO_WORKER)) {
-#ifdef CONFIG_X86_32
- task_user_gs(p) = get_user_gs(current_pt_regs());
-#endif
-
+ if (unlikely(args->fn)) {
/*
- * An IO thread is a user space thread, but it doesn't
- * return to ret_after_fork().
+ * A user space thread, but it doesn't return to
+ * ret_after_fork().
*
* In order to indicate that to tools like gdb,
* we reset the stack and instruction pointers.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2022-05-09 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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