From: Kingsley Cheung <kingsley@aurema.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Trivial Patch] Bad tgid and tid lookup for /proc
Date: Mon, 15 Mar 2004 09:46:18 +1100 [thread overview]
Message-ID: <20040315094618.A19791@aurema.com> (raw)
In-Reply-To: <20040312005401.DD4032C733@lists.samba.org>; from rusty@rustcorp.com.au on Fri, Mar 12, 2004 at 09:09:09AM +1100
On Fri, Mar 12, 2004 at 09:09:09AM +1100, Rusty Russell wrote:
> In message <20040209135110.H17768@aurema.com> you write:
> > All,
> >
> > On 2.6.2, one can do the following, which is clearly wrong:
> >
> > gen2 02:49:45 ~: cat /proc/1/task/$$/stat
> > 1669 (bash) S 1668 1669 1669 34816 1730 256 1480 6479 12 4 8 5 5 17 15 0 1 0
> 8065 3252224 451 4294967295 134512640 134955932 3221225104 3221222840 429496014
> 4 0 65536 3686404 1266761467 3222442959 0 0 17 0 0 0
> > gen2 02:50:44 ~: ls /proc/1/task
> > 1
>
> Patch was mangled, and IMHO wasn't exactly trivial. As I understand
> it, you could access any task under /proc/xxx/task. Your patch seems to
> make it that you can access any task under /proc/xxx/task if xxx is a
> thread group leader.
>
> A little confused,
> Rusty.
Rusty,
Andrew Morton, Peter Chubb, and a few others actually had a discussion
and resolved some issues around that patch. So thanks to them I guess
there's no need to be confused ;)
Thanks for looking at it anyway.
--
Kingsley
prev parent reply other threads:[~2004-03-14 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 2:51 [Trivial Patch] Bad tgid and tid lookup for /proc Kingsley Cheung
2004-03-11 22:09 ` Rusty Russell
2004-03-14 22:46 ` Kingsley Cheung [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=20040315094618.A19791@aurema.com \
--to=kingsley@aurema.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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