From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: akpm@linux-foundation.org, pavel@ucw.cz, joe@perches.com,
keescook@chromium.org, geert@linux-m68k.org, jkosina@suse.cz,
viro@zeniv.linux.org.uk, davem@davemloft.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/vsprintf: add %pT format specifier
Date: Sat, 11 Jan 2014 01:50:45 -0800 [thread overview]
Message-ID: <20140111095045.GD10038@linux.vnet.ibm.com> (raw)
In-Reply-To: <201401111209.IEG82331.OtVQLFOFHMOSFJ@I-love.SAKURA.ne.jp>
On Sat, Jan 11, 2014 at 12:09:46PM +0900, Tetsuo Handa wrote:
> Andrew Morton wrote:
> > In the absence of step 3, steps 1 and 2 are rather pointless churn.
> >
> > So I think it would be better to merge (into mainline) steps 1 and 3
> > first and at the same time. Then start thinking about step 2.
>
> Unfortunately we can't.
> Step 2 depends on step 1 for avoiding compile time errors.
> Step 3 depends on step 2 for avoiding run time errors.
>
> Step 1: (targeted to 3.14-rc1)
> Add "%pT" format specifier and commcpy() wrapper function.
>
> Step 2: (started after step 1 is reflected to other git trees)
> Replace printk("%s", current->comm) with printk("%pT", NULL).
> Replace printk("%s", p->comm) with printk("%pT", p).
> Replace strcpy(buf, p->comm) with commcpy(buf, p).
>
> Step 3: (started after step 2 is reflected to other git trees)
> Add rcu_read_lock()/rcu_read_unlock() into commcpy().
> Modify set_task_comm() etc. to replace ->comm using RCU.
>
> If step 3 is merged into mainline before step 2 complete, those who are not
> using "%pT" or commcpy() might crash due to reading RCU protected ->comm
> without rcu_read_lock()/rcu_read_unlock().
>
>
> Let me confirm, Paul.
>
> I'm trying to change task_struct->comm to use RCU.
> At step 3, I'm planning to do
>
> static inline void *commcpy(void *buf, const struct task_struct *tsk)
> {
> rcu_read_lock();
> memcpy(buf, tsk->comm, TASK_COMM_LEN);
> rcu_read_unlock();
> return buf;
> }
>
> and let set_task_comm() wait for readers using synchronize_rcu() or
> call_rcu().
>
> Given that commcpy() can be called from any context, are synchronize_rcu()
> and call_rcu() sufficient for waiting for commcpy() users?
Yep, that should work.
Thanx, Paul
next prev parent reply other threads:[~2014-01-11 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 12:52 [PATCH] lib/vsprintf: add %pT format specifier Tetsuo Handa
2014-01-09 18:11 ` Kees Cook
2014-01-10 23:59 ` Andrew Morton
2014-01-11 1:59 ` Tetsuo Handa
2014-01-11 2:15 ` Joe Perches
2014-01-11 2:30 ` Tetsuo Handa
2014-01-11 10:28 ` Geert Uytterhoeven
2014-01-11 12:03 ` Tetsuo Handa
2014-01-11 0:04 ` Andrew Morton
2014-01-11 1:28 ` Tetsuo Handa
2014-01-11 1:36 ` Joe Perches
2014-01-11 1:48 ` Tetsuo Handa
2014-01-11 1:57 ` Andrew Morton
2014-01-11 3:09 ` Tetsuo Handa
2014-01-11 9:50 ` Paul E. McKenney [this message]
2014-01-11 11:35 ` Pavel Machek
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=20140111095045.GD10038@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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