From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 4/12 v2] ptrace: introduce the empty "struct ptrace_context"
Date: Fri, 29 May 2009 13:53:06 +0200 [thread overview]
Message-ID: <20090529115306.GA19812@redhat.com> (raw)
In-Reply-To: <20090528211540.2A5BAFC2BD@magilla.sf.frob.com>
On 05/28, Roland McGrath wrote:
>
> > + task_lock(tsk);
> > + if (likely(!tsk->ptrace_ctx))
> > + tsk->ptrace_ctx = ptrace_ctx;
> > + else
> > + kfree(ptrace_ctx);
> > + task_unlock(tsk);
>
> I don't think it's kosher call kfree with task_lock() held.
Yes, it always makes sense to move as much as possible outside of
spin_lock/etc, but
> The kfree case is a very unlikely path,
Exactly, this kfree() "never" runs under task_lock(), but the code
looks a bit simpler and shorter.
> so it can be:
>
> task_lock(tsk);
> if (likely(!tsk->ptrace_ctx)) {
> tsk->ptrace_ctx = ptrace_ctx;
> task_unlock(tsk);
> return 0;
> }
>
> task_unlock(tsk);
> kfree(ptrace_ctx);
OK, will change.
Oleg.
prev parent reply other threads:[~2009-05-29 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 11:35 [RFC PATCH 4/12 v2] ptrace: introduce the empty "struct ptrace_context" Oleg Nesterov
2009-05-28 21:15 ` Roland McGrath
2009-05-29 11:53 ` 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=20090529115306.GA19812@redhat.com \
--to=oleg@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
/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