From: Bill Davidsen <davidsen@tmr.com>
To: Sripathi Kodi <sripathik@in.ibm.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, patrics@interia.pl,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH 2.6.13.1] Patch for invisible threads
Date: Wed, 14 Sep 2005 10:37:40 -0400 [thread overview]
Message-ID: <432835B4.7070405@tmr.com> (raw)
In-Reply-To: <43278116.8020403@in.ibm.com>
Sripathi Kodi wrote:
> Linus Torvalds wrote:
>
>> I don't think this is wrong per se, but you shouldn't take the
>> tasklist lock normally. You're better off just doing
>
>
> Linus,
>
> I incarporated the path that doesn't hold tasklist lock unnecessarily.
> The patch is below. This seems to work without any problems for me.
>
> If the decision is to remove ->permission, I can send a small patch I
> have that removes .permission entry from proc_task_inode_operations.
> Either way fixes the problem I found.
Let me say that this solution, and any other which loops through all
threads of a task, isn't going to scale well. I don't have a magic O(1)
solution, if it were easy someone would have done that instead of the
while loop, just noting that a clever solution would be a win on servers.
>
> Thanks and regards,
> Sripathi.
>
> Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
>
> --- linux-2.6.13.1-orig/fs/proc/base.c 2005-09-14 03:46:22.000000000
> -0500
> +++ linux-2.6.13.1/fs/proc/base.c 2005-09-14 03:48:35.000000000 -0500
> @@ -275,11 +275,33 @@ static int proc_root_link(struct inode *
> {
> struct fs_struct *fs;
> int result = -ENOENT;
> - task_lock(proc_task(inode));
> - fs = proc_task(inode)->fs;
> - if(fs)
> + struct task_struct *leader = proc_task(inode);
> +
> + task_lock(leader);
> + fs = leader->fs;
> + if (fs) {
> atomic_inc(&fs->count);
> - task_unlock(proc_task(inode));
> + task_unlock(leader);
> + } else {
> + /* Try to get fs from sub-threads */
> + task_unlock(leader);
> + struct task_struct *task = leader;
> + read_lock(&tasklist_lock);
> + if (pid_alive(task)) {
> + while ((task = next_thread(task)) != leader) {
> + task_lock(task);
> + fs = task->fs;
> + if (fs) {
> + atomic_inc(&fs->count);
> + task_unlock(task);
> + break;
> + }
> + task_unlock(task);
> + }
> + }
> + read_unlock(&tasklist_lock);
> + }
> +
> if (fs) {
> read_lock(&fs->lock);
> *mnt = mntget(fs->rootmnt);
>
next prev parent reply other threads:[~2005-09-14 14:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 17:46 [PATCH 2.6.13.1] Patch for invisible threads Sripathi Kodi
2005-09-12 20:49 ` Andrew Morton
2005-09-13 13:10 ` Sripathi Kodi
2005-09-13 14:53 ` Linus Torvalds
2005-09-13 16:51 ` Al Viro
2005-09-13 17:01 ` Linus Torvalds
2005-09-13 17:12 ` Al Viro
2005-09-13 21:30 ` Sripathi Kodi
2005-09-13 21:56 ` Roland McGrath
2005-09-13 21:57 ` Al Viro
2005-09-13 23:10 ` Linus Torvalds
2005-09-14 1:47 ` Sripathi Kodi
2005-09-14 1:52 ` Al Viro
2005-09-14 14:37 ` Bill Davidsen [this message]
2005-09-15 0:30 ` Sripathi Kodi
2005-09-14 1:50 ` Al Viro
2005-09-15 0:31 ` Sripathi Kodi
2005-09-15 0:55 ` Roland McGrath
2005-09-15 1:38 ` Sripathi Kodi
2005-09-15 2:12 ` Al Viro
2005-09-15 7:29 ` Roland McGrath
2005-09-15 1:18 ` Al Viro
2005-09-16 0:54 ` Sripathi Kodi
2005-09-16 7:46 ` Al Viro
2005-09-16 15:06 ` Sripathi Kodi
2005-09-16 18:05 ` Daniel Jacobowitz
2005-09-16 18:14 ` Al Viro
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=432835B4.7070405@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=patrics@interia.pl \
--cc=roland@redhat.com \
--cc=sripathik@in.ibm.com \
--cc=viro@ZenIV.linux.org.uk \
/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