From: Alexey Dobriyan <adobriyan@gmail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] utrace core
Date: Sat, 30 Aug 2008 19:05:45 +0400 [thread overview]
Message-ID: <20080830150545.GA29686@x200.localdomain> (raw)
In-Reply-To: <20080826220157.397C7154233@magilla.localdomain>
On Tue, Aug 26, 2008 at 03:01:57PM -0700, Roland McGrath wrote:
> +/**
> + * struct utrace_attached_engine - per-engine structure
> + * @ops: &struct utrace_engine_ops pointer passed to utrace_attach_task()
> + * @data: engine-private &void * passed to utrace_attach_task()
> + * @flags: event mask set by utrace_set_events() plus internal flag bits
> + *
> + * The task itself never has to worry about engines detaching while
> + * it's doing event callbacks. These structures are removed from the
> + * task's active list only when it's stopped, or by the task itself.
> + *
> + * utrace_engine_get() and utrace_engine_put() maintain a reference count.
> + * When it drops to zero, the structure is freed. One reference is held
> + * implicitly while the engine is attached to its task.
> + */
> +struct utrace_attached_engine {
> +/* private: */
> + struct kref kref;
Engine grew a refcount.
Was it added to fix some bug?
Old utrace git doesn't have this, new utrace git has only two
posted patches, so asking.
next prev parent reply other threads:[~2008-08-30 15:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 22:01 [PATCH 0/2] utrace Roland McGrath
2008-08-26 22:01 ` [PATCH 1/2] utrace core Roland McGrath
2008-08-26 22:55 ` Alexey Dobriyan
2008-08-27 21:32 ` Alexey Dobriyan
2008-08-27 21:46 ` Alexey Dobriyan
2008-08-27 22:00 ` Alexey Dobriyan
2008-08-30 13:45 ` Christoph Hellwig
2008-09-03 12:11 ` Roland McGrath
2008-09-03 17:01 ` Alexey Dobriyan
2008-08-27 20:04 ` Alexey Dobriyan
2008-09-03 12:11 ` Roland McGrath
2008-09-03 18:44 ` Christoph Hellwig
2008-08-30 15:05 ` Alexey Dobriyan [this message]
2008-09-03 12:58 ` Petr Tesarik
2008-09-03 18:08 ` Roland McGrath
2008-09-03 18:46 ` Christoph Hellwig
2008-09-04 9:03 ` Petr Tesarik
2008-08-26 22:02 ` [PATCH 2/2] utrace: ptrace cooperation Roland McGrath
2008-08-30 13:38 ` Christoph Hellwig
2008-09-03 12:10 ` Roland McGrath
2008-09-03 18:41 ` Christoph Hellwig
2008-08-26 22:34 ` [PATCH 0/2] utrace Alexey Dobriyan
2008-08-26 22:39 ` Christoph Hellwig
2008-08-27 0:17 ` Frank Ch. Eigler
2008-08-27 13:54 ` Christoph Hellwig
2008-08-27 16:40 ` Ananth N Mavinakayanahalli
2008-08-30 13:40 ` Christoph Hellwig
2008-09-03 12:09 ` Roland McGrath
2008-09-03 18:37 ` Christoph Hellwig
2008-08-27 15:34 ` Alexey Dobriyan
2008-08-29 19:04 ` Frank Ch. Eigler
2008-08-30 13:43 ` Christoph Hellwig
2008-08-27 18:50 ` Alexey Dobriyan
2008-08-27 2:03 ` Peter Zijlstra
2008-10-06 20:47 ` Peter Zijlstra
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=20080830150545.GA29686@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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