From: Oleg Nesterov <oleg@tv-sign.ru>
To: Jean Delvare <jdelvare@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] proc: bye bye tasklist_lock
Date: Mon, 11 Sep 2006 22:29:56 +0400 [thread overview]
Message-ID: <20060911182956.GA246@oleg> (raw)
In-Reply-To: <200609111319.42132.jdelvare@suse.de>
On 09/11, Jean Delvare wrote:
> Hi Oleg,
>
> On Sunday 10 September 2006 00:18, Oleg Nesterov wrote:
> > fs/proc/ does not use tasklist_lock anymore.
> >
> > These patches are simple enough and do not depend on each other.
> > The only problem I don't know how to really test them.
>
> Just to make sure I understand what it is all about: Is there a relation
> between this patchset and the recent patch from Eric fixing the
> readdir(/proc) race?
No, they are not related. This series doesn't fix bugs, just
removes tasklist_lock from fs/proc/ entirely.
Oleg.
prev parent reply other threads:[~2006-09-11 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 22:18 [PATCH 0/3] proc: bye bye tasklist_lock Oleg Nesterov
2006-09-11 11:19 ` Jean Delvare
2006-09-11 18:29 ` 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=20060911182956.GA246@oleg \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=jdelvare@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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