DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gN/gSJL7t0DLOzEFhUYnRyBWGmFXDTh9fqO/gaSpvYcIHlpljPzEtULnSDTW6IPYJydGVSTiHgd8FM7KGdO1bpMELT81Sd2YmCFV6pdjB5zDM3nYn9VoYjsAVFXduQ2a/G/rpA8NtNG7/oprI0YCmvtpXQk5K9vrGp7QtgLNopI=
Message-ID: <67029b170602141939v4791ac72l@mail.gmail.com>
Date: Wed, 15 Feb 2006 11:39:26 +0800
From: Zhou Yingchao <yingchao.zhou@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: [PATCH] kretprobe instance recycled by parent process
In-Reply-To: <67029b170602141936v69b85832q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <43F3059A.9070601@linux.intel.com>
	 <67029b170602141936v69b85832q@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1117
Lines: 29

2006/2/15, bibo mao <bibo_mao@linux.intel.com>:
> When kretprobe probe schedule() function, if probed process exit then
> schedule() function will never return, so some kretprobe instance will
> never be recycled. By this patch the parent process will recycle
> retprobe instance of probed function, there will be no memory leak of
> kretprobe instance. This patch is based on 2.6.16-rc3.

Is there any process which can exit without go through the do_exit() path?
--
Yingchao Zhou
***********************************************
 Institute Of Computing Technology
 Chinese Academy of Sciences
 Tel(O) : 010-62613792-28
***********************************************


--
Yingchao Zhou
***********************************************
 Institute Of Computing Technology
 Chinese Academy of Sciences
 Tel(O) : 010-62613792-28
***********************************************
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/