All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Memory leak in 2.5.64
Date: Wed, 12 Mar 2003 06:55:12 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806052@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806020@msgid-missing>

>>>>> On Mon, 10 Mar 2003 19:59:39 -0800, William Lee Irwin III <wli@holomorphy.com> said:

  William> On Tue, Mar 11, 2003 at 02:44:14PM +1100, Peter Chubb
  William> wrote:
  >> The way that tasks need to be freed has changed since 2.5.61 ---
  >> I think we need to do something like the attached patch (keep
  >> __put_task_struct() in kernel/fork.c; have ia64-specific
  >> free_task_struct() in arch/ia64/kernel/process.c) otherwise the
  >> user_struct will never have its reference count deleted and so
  >> will not be freed.

  William> I think you might be in trouble. From entry.S:

  William>         /* * Invoke schedule_tail(task) while preserving
  William> in0-in7, which may be nee ded * in case a system call gets
  William> restarted.  */ GLOBAL_ENTRY(ia64_invoke_schedule_tail)

  William> Well, you're going to need to pass a parameter to
  William> schedule_tail() namely, the previous task, and find some
  William> other way to save in0-in7.  schedule_tail() now relies on
  William> the task getting passed to it to free it.

That's why ia64_invoke_schedule_tail() exists in the first place: the
previously running task is passed in r8.  In other words: no problem.

	--david


      reply	other threads:[~2003-03-12  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  3:44 [Linux-ia64] Memory leak in 2.5.64 Peter Chubb
2003-03-12  6:55 ` David Mosberger [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=marc-linux-ia64-105590709806052@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.