Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762534AbZDCLIm (ORCPT ); Fri, 3 Apr 2009 07:08:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761088AbZDCLIb (ORCPT ); Fri, 3 Apr 2009 07:08:31 -0400 Received: from mx2.redhat.com ([66.187.237.31]:54288 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758904AbZDCLIa (ORCPT ); Fri, 3 Apr 2009 07:08:30 -0400 Message-ID: <49D5EE1F.4060009@redhat.com> Date: Fri, 03 Apr 2009 13:08:15 +0200 From: Gerd Hoffmann User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Izik Eidus CC: Chris Wright , Anthony Liguori , Andrea Arcangeli , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-mm@kvack.org, avi@redhat.com, riel@redhat.com, jeremy@goop.org, mtosatti@redhat.com, hugh@veritas.com, corbet@lwn.net, yaniv@redhat.com, dmonakhov@openvz.org Subject: Re: [PATCH 5/4] update ksm userspace interfaces References: <20090331142533.GR9137@random.random> <49D22A9D.4050403@codemonkey.ws> <20090331150218.GS9137@random.random> <49D23224.9000903@codemonkey.ws> <20090331151845.GT9137@random.random> <49D23CD1.9090208@codemonkey.ws> <20090331162525.GU9137@random.random> <49D24A02.6070000@codemonkey.ws> <20090402012215.GE1117@x200.localdomain> <49D424AF.3090806@codemonkey.ws> <20090402053114.GF1117@x200.localdomain> <49D4BE64.8020508@redhat.com> <49D5E1EE.6030707@redhat.com> <49D5E9B5.1020101@redhat.com> In-Reply-To: <49D5E9B5.1020101@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 934 Lines: 28 Izik Eidus wrote: > Gerd Hoffmann wrote: >> Did you test whenever it really cleans up in case you "kill -9 qemu"? >> >> I recently did something simliar with the result that the extra >> reference hold on mm_struct prevented the process memory from being >> zapped ... >> >> cheers, >> Gerd >> > Did you use mmput() after you called get_task_mm() ??? > get_task_mm() do nothing beside atomic_inc(&mm->mm_users); mmput() call was in ->release() callback, ->release() in turn never was called because the kernel didn't zap the mappings because of the reference ... The driver *also* created mappings which ksmctl doesn't, so it could be you don't run into this issue. cheers, Gerd -- 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/