From: Li Zefan <lizf@cn.fujitsu.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] trace_workqueue: add refcnt to struct cpu_workqueue_stats
Date: Tue, 07 Jul 2009 16:23:40 +0800 [thread overview]
Message-ID: <4A53060C.5010605@cn.fujitsu.com> (raw)
In-Reply-To: <20090707080755.GC6173@nowhere>
Frederic Weisbecker wrote:
> On Tue, Jul 07, 2009 at 02:07:35PM +0800, Li Zefan wrote:
>>> The stat entries can be freed when the stat file is being read.
>>> The worse is, the ptr can be freed immediately after it's returned
>>> from workqueue_stat_start/next().
>>>
>>> Add a refcnt to struct cpu_workqueue_stats to avoid use-after-free.
>>>
>>> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>>> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
>>> ---
>> ...
>>> @@ -175,11 +184,14 @@ static void *workqueue_stat_next(void *prev, int idx)
>>> return NULL;
>>> } while (!(ret = workqueue_stat_start_cpu(cpu)));
>>> return ret;
>>> + } else {
>>> + ret = list_entry(prev_cws->list.next,
>>> + struct cpu_workqueue_stats, list);
>> I just realized accessing prev_cws->list.next can be invalid!
>>
>> We can fix it by using list_del_init() to delete cws->list in
>> probe_workqueue_destruction(), but then if the race happened,
>> the next time stat_next() is called, NULL will be returned.
>> I guess this is Ok, since the race is rare.
>
>
> If you ensure the kref_get/put are under the
> workqueue_cpu_stat(cpu)->lock, it should be fine, right?
>
Unfortunately no.
It's safe to dereference prev_cws, but not safe to retreive
prevw_cws->list.next.
Suppose: head->n1->n2
T1 T2
--------------- -------------------
stat_start()
-> return n1
list_del(n1)
-> n1->list->next = LIST_POISON1;
stat_next()
-> prev = n1
-> list_entry(prev->list.next) !!!
You see why it's not safe..
>
>> (I never like the design of trace_stat..Fortunately we'll
>> probably switch to perfcounter for this kind of statistics
>> reporting)
>
>
> I don't like its design either. I wrote it specifically for
> the branch tracer and didn't think about free-able events :-/
>
Yeah, for free-able events it's buggy to use trace_stat.
Similar bug exists in ksym_tracer.
Another way to fix it is not use trace_stat but use seq_file
directly. They don't need to be sorted anyway.
next prev parent reply other threads:[~2009-07-07 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 8:10 [PATCH 2/2] trace_workqueue: add refcnt to struct cpu_workqueue_stats Li Zefan
2009-07-07 6:07 ` Li Zefan
2009-07-07 8:07 ` Frederic Weisbecker
2009-07-07 8:23 ` Li Zefan [this message]
2009-07-10 10:42 ` [tip:tracing/core] tracing/workqueues: Add " tip-bot for Lai Jiangshan
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=4A53060C.5010605@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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