From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Josh Triplett <josht@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [PATCH] rcu: Avoid kthread_stop on invalid pointer if rcutorture reader startup fails
Date: Wed, 16 Aug 2006 16:37:54 -0700 [thread overview]
Message-ID: <20060816233754.GD1291@us.ibm.com> (raw)
In-Reply-To: <1155767042.9175.41.camel@josh-work.beaverton.ibm.com>
On Wed, Aug 16, 2006 at 03:24:02PM -0700, Josh Triplett wrote:
> rcu_torture_init kmallocs the array of reader threads, then creates each one
> with kthread_run, cleaning up with rcu_torture_cleanup if this fails.
> rcu_torture_cleanup calls kthread_stop on any non-NULL pointer in the array;
> however, any readers after the one that failed to start up will have invalid
> pointers, not null pointers. Avoid this by using kzalloc instead.
Good catch!!!
Acked-by: Paul E. McKenney <paulmck@us.ibm.com>
> Signed-off-by: Josh Triplett <josh@freedesktop.org>
> ---
> kernel/rcutorture.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/rcutorture.c b/kernel/rcutorture.c
> index aff0064..8b09c95 100644
> --- a/kernel/rcutorture.c
> +++ b/kernel/rcutorture.c
> @@ -779,7 +779,7 @@ rcu_torture_init(void)
> writer_task = NULL;
> goto unwind;
> }
> - reader_tasks = kmalloc(nrealreaders * sizeof(reader_tasks[0]),
> + reader_tasks = kzalloc(nrealreaders * sizeof(reader_tasks[0]),
> GFP_KERNEL);
> if (reader_tasks == NULL) {
> VERBOSE_PRINTK_ERRSTRING("out of memory");
> --
> 1.4.1.1
>
>
prev parent reply other threads:[~2006-08-16 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 22:24 [PATCH] rcu: Avoid kthread_stop on invalid pointer if rcutorture reader startup fails Josh Triplett
2006-08-16 23:37 ` Paul E. McKenney [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=20060816233754.GD1291@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=josht@us.ibm.com \
--cc=linux-kernel@vger.kernel.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