All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@sw.ru>
To: Christoph Hellwig <hch@lst.de>, Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH -utrace] Move utrace into task_struct
Date: Tue, 8 May 2007 18:42:37 +0400	[thread overview]
Message-ID: <20070508144237.GB6130@localhost.sw.ru> (raw)
In-Reply-To: <20070503103449.GB6147@lst.de>

Regardless of future of "struct utrace utrace;" patch looks like there
is another race: engine's flags and ops settings in utrace_detach() and
acting on them in report_quiescent():

utrace_detach()				report_quiescent()
---------------				------------------
[utrace lock held]			[utrace lock is not held]

engine->flags = UTRACE_EVENT(QUIESCE) |
		UTRACE_ACTION_QUIESCE;
					if (engine->flags & UTRACE_EVENT(QUIESCE))
						REPORT(report_quiesce);

rcu_assign_pointer(engine->ops, &dead_engine_ops);


At the moment of REPORT call engine's ops are still "live" ptrace ops
which do not have ->report_quiesce callback. So, there will oops while
calling function at NULL address. "Dead" ptrace engine ops do have dummy
callback but it wasn't yet glued.

I hit this once with "struct utrace utrace;" patch applied, but this
bug is also present in stock utrace, I'm sure.


      reply	other threads:[~2007-05-08 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 11:32 [PATCH -utrace] Move utrace into task_struct Alexey Dobriyan
2007-05-02 11:53 ` Jan Engelhardt
2007-05-02 22:02 ` Roland McGrath
2007-05-03 10:34   ` Christoph Hellwig
2007-05-08 14:42     ` Alexey Dobriyan [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=20070508144237.GB6130@localhost.sw.ru \
    --to=adobriyan@sw.ru \
    --cc=devel@openvz.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.