From: Oleg Nesterov <oleg@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Kees Cook <keescook@chromium.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>, Petr Skocik <pskocik@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jens Axboe <axboe@kernel.dk>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
Frederic Weisbecker <frederic@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Mike Christie <michael.christie@oracle.com>,
Marco Elver <elver@google.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"haifeng.xu" <haifeng.xu@shopee.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] [RFC] signal: Add KUnit tests
Date: Thu, 17 Aug 2023 18:17:18 +0200 [thread overview]
Message-ID: <20230817161718.GA4121@redhat.com> (raw)
In-Reply-To: <87bkf68g5m.fsf@email.froward.int.ebiederm.org>
On 08/16, Eric W. Biederman wrote:
>
> Arguably we can skip this as well. There are only 3 uses of
> do_each_thread (pivot_root, SAK, and ia64 backtrace) and they all should
> be changed to be for_each_process_thread.
Hmm. I thought that do_each_thread() was already killed ...
Let me send the trivial patch.
We also need to kill (or rework) while_each_thread() and next_thread(),
I'll try to do this tomorrow.
Oleg.
next prev parent reply other threads:[~2023-08-17 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 21:05 [PATCH] [RFC] signal: Add KUnit tests Kees Cook
2023-08-17 4:08 ` Eric W. Biederman
2023-08-17 16:17 ` Oleg Nesterov [this message]
2023-08-17 16:57 ` Kees Cook
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=20230817161718.GA4121@redhat.com \
--to=oleg@redhat.com \
--cc=axboe@kernel.dk \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=haifeng.xu@shopee.com \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mcgrof@kernel.org \
--cc=michael.christie@oracle.com \
--cc=peterz@infradead.org \
--cc=pskocik@gmail.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.