From: Mike Christie <michael.christie@oracle.com>
To: hch@infradead.org, stefanha@redhat.com, jasowang@redhat.com,
mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org, brauner@kernel.org,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Cc: Mike Christie <michael.christie@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH v10 4/8] fork: Add USER_WORKER flag to ignore signals
Date: Sun, 19 Jun 2022 20:13:53 -0500 [thread overview]
Message-ID: <20220620011357.10646-5-michael.christie@oracle.com> (raw)
In-Reply-To: <20220620011357.10646-1-michael.christie@oracle.com>
From: Christian Brauner <brauner@kernel.org>
Since:
commit 10ab825bdef8 ("change kernel threads to ignore signals instead of
blocking them")
kthreads have been ignoring signals by default, and the vhost layer has
never had a need to change that. This patch adds an option flag,
USER_WORKER_SIG_IGN, handled in copy_process() after copy_sighand()
and copy_signals() so vhost_tasks added in the next patches can continue
to ignore singals.
Signed-off-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Mike Christie <michael.christie@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
---
include/linux/sched/task.h | 1 +
kernel/fork.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/include/linux/sched/task.h b/include/linux/sched/task.h
index 7f6364e5aa1a..9fbb489b2512 100644
--- a/include/linux/sched/task.h
+++ b/include/linux/sched/task.h
@@ -21,6 +21,7 @@ struct css_set;
#define USER_WORKER BIT(0)
#define USER_WORKER_IO BIT(1)
#define USER_WORKER_NO_FILES BIT(2)
+#define USER_WORKER_SIG_IGN BIT(3)
struct kernel_clone_args {
u64 flags;
diff --git a/kernel/fork.c b/kernel/fork.c
index 0313aa9ead89..c479b8419a6e 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -2261,6 +2261,9 @@ static __latent_entropy struct task_struct *copy_process(
if (retval)
goto bad_fork_cleanup_io;
+ if (args->worker_flags & USER_WORKER_SIG_IGN)
+ ignore_signals(p);
+
stackleak_task_init(p);
if (pid != &init_struct_pid) {
--
2.25.1
next prev parent reply other threads:[~2022-06-20 1:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 1:13 [PATCH v10 0/8] Use copy_process in vhost layer Mike Christie
2022-06-20 1:13 ` [PATCH v10 1/8] fork: Make IO worker options flag based Mike Christie
2022-06-20 1:13 ` [PATCH v10 2/8] fork/vm: Move common PF_IO_WORKER behavior to new flag Mike Christie
2022-06-20 1:13 ` [PATCH v10 3/8] fork: add USER_WORKER flag to not dup/clone files Mike Christie
2022-06-20 1:13 ` Mike Christie [this message]
2022-06-20 1:13 ` [PATCH v10 5/8] fork: allow kernel code to call copy_process Mike Christie
2022-06-20 1:13 ` [PATCH v10 6/8] vhost_task: Allow vhost layer to use copy_process Mike Christie
2022-06-20 1:13 ` [PATCH v10 7/8] vhost: move worker thread fields to new struct Mike Christie
2022-06-20 1:13 ` [PATCH v10 8/8] vhost: use vhost_tasks for worker threads Mike Christie
2022-07-12 4:44 ` [PATCH v10 0/8] Use copy_process in vhost layer Mike Christie
2022-07-12 4:54 ` Christoph Hellwig
2022-07-14 13:02 ` Christian Brauner
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=20220620011357.10646-5-michael.christie@oracle.com \
--to=michael.christie@oracle.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®