Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: 8BIT
Subject: RE: hugetlb bug
Date: Wed, 18 Jan 2006 16:46:34 +0800
Message-ID: <8126E4F969BA254AB43EA03C59F44E840483E8D4@pdsmsx404>
Thread-Topic: hugetlb bug
Thread-Index: AcYcCvoWXG33z6kYTnmsPggyzhOoFQAAFrCQ
From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: "William Lee Irwin III" <wli@holomorphy.com>,
       "HuaFeijun" <hua.feijun@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1281
Lines: 24

>>-----Original Message-----
>>From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of William Lee Irwin III
>>Sent: 2006??1??18?? 16:37
>>To: HuaFeijun
>>Cc: linux-kernel@vger.kernel.org
>>Subject: Re: hugetlb bug
>>
>>On Wed, Jan 18, 2006 at 04:00:03PM +0800, HuaFeijun wrote:
>>> Is it kernel bug? The code works normally on ia64 machine,howerver, on
>>> EM64T,it fails tot work.
>>> The function call of shmat will change /proc/meminfo;and  the shmdt
>>> can't restore it to original content.  How to restore it to original
>>> stauts?Thanks.
>>> Is it kernel bug? The code works normally on ia64 machine,howerver,
>>> on EM64T,it fails tot work. The function call of shmat will change
>>> /proc/meminfo file's content;and  the shmdt can't restore the file's
>>> content.  How to restore it to original stauts?Thanks.
Did you check ipc? Command 'ipcs -a" could show all shared memory. I guess you app doesn't call shmctl(..., IPC_RMID, ...) after shmdt. Use ipcrm to release them manually.

-
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/