From: Oleg Nesterov <oleg@redhat.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: dserrg@gmail.com, snanda@chromium.org, rientjes@google.com,
linux-kernel@vger.kernel.org
Subject: Re: Question about replacing while_each_thread().
Date: Wed, 1 Feb 2017 18:19:11 +0100 [thread overview]
Message-ID: <20170201171911.GA18136@redhat.com> (raw)
In-Reply-To: <201702011947.DBD56740.OMVHOLOtSJFFFQ@I-love.SAKURA.ne.jp>
Hi Tetsuo,
On 02/01, Tetsuo Handa wrote:
>
> Is rcu_read_lock() sufficient (i.e.
>
> rcu_read_lock();
> for_each_process_thread(g, p) {
> (...snipped...)
> }
> rcu_read_unlock();
>
> is OK) for "can't go away" ?
Yes, this should work just fine,
> Likewise, IOPRIO_WHO_PGRP case are using
>
> rcu_read_lock();
> do {
> if ((pgrp) != NULL)
> hlist_for_each_entry_rcu((p), &(pgrp)->tasks[PIDTYPE_PGID], pids[PIDTYPE_PGID].node) {
> {
> struct task_struct *tg___ = p;
> do {
> (...snipped...)
> } while_each_thread(tg___, p);
> p = tg___;
> }
> if (PIDTYPE_PGID == PIDTYPE_PID)
> break;
> }
> } while (0);
> rcu_read_unlock();
>
> sequence which I guess it is unsafe as well.
Hmm, indeed, I forgot there is another while_each_thread() hidden in
do_each_pid_thread()
> In this case updating do_each_pid_thread() to use for_each_thread() and
> updating while_each_pid_thread() not to use while_each_thread() is
> the correct fix?
Yes, I think so, just
--- a/include/linux/pid.h
+++ b/include/linux/pid.h
@@ -191,10 +191,10 @@ pid_t pid_vnr(struct pid *pid);
#define do_each_pid_thread(pid, type, task) \
do_each_pid_task(pid, type, task) { \
struct task_struct *tg___ = task; \
- do {
+ for_each_thread(tg__, task) {
#define while_each_pid_thread(pid, type, task) \
- } while_each_thread(tg___, task); \
+ } \
task = tg___; \
} while_each_pid_task(pid, type, task)
#endif /* _LINUX_PID_H */
but perhaps we can also cleanup it... the usage of 'tg___' doesn't look nice
either way, so perhaps
#define do_each_pid_thread(pid, type, task) do { \
struct task_struct *tg___; \
do_each_pid_task(pid, type, tg___) { \
for_each_thread(tg__, task) {
#define while_each_pid_thread(pid, type, task) \
} \
} while_each_pid_task(pid, type, task); \
} while (0)
will look a bit better? up to you.
Oleg.
prev parent reply other threads:[~2017-02-01 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 10:47 Tetsuo Handa
2017-02-01 17:19 ` Oleg Nesterov [this message]
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=20170201171911.GA18136@redhat.com \
--to=oleg@redhat.com \
--cc=dserrg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.com \
--cc=snanda@chromium.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
Powered by JetHome