From: Christoph Hellwig <hch@lst.de>
To: Roland McGrath <roland@redhat.com>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
akpm@osdl.org, hch@lst.de, linux-kernel@vger.kernel.org,
devel@openvz.org
Subject: Re: [PATCH -utrace] Move utrace into task_struct
Date: Thu, 3 May 2007 12:34:49 +0200 [thread overview]
Message-ID: <20070503103449.GB6147@lst.de> (raw)
In-Reply-To: <20070502220203.D73D21801A3@magilla.sf.frob.com>
On Wed, May 02, 2007 at 03:02:03PM -0700, Roland McGrath wrote:
> That's just a workaround for an actual bug that I need to fix.
> You wouldn't really want to do it that way.
It's actuall a very nice and needed simplification. It gets rid
of an object with subtle life time rules, which is always a good
thing. The utrace code really needs more patches in the style
of Alexey's as this kind of overengineering is what will cause
hard to debug problems over the long run.
next prev parent reply other threads:[~2007-05-03 10:35 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 [this message]
2007-05-08 14:42 ` Alexey Dobriyan
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=20070503103449.GB6147@lst.de \
--to=hch@lst.de \
--cc=adobriyan@sw.ru \
--cc=akpm@osdl.org \
--cc=devel@openvz.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox