From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tejun Heo <tj@kernel.org>
Date: Fri, 1 Feb 2013 10:00:28 -0800
Subject: [Cluster-devel] [PATCH 10/14] dlm: don't use idr_remove_all()
In-Reply-To: <20130201174443.GC3812@redhat.com>
References: <1359163872-1949-1-git-send-email-tj@kernel.org>
	<1359163872-1949-11-git-send-email-tj@kernel.org>
	<20130128155723.GC16789@redhat.com>
	<20130129151317.GA11609@redhat.com>
	<20130130212417.GJ24014@redhat.com>
	<20130131235320.GN6824@mtj.dyndns.org>
	<20130201001841.GP6824@mtj.dyndns.org>
	<20130201174443.GC3812@redhat.com>
Message-ID: <20130201180028.GC31863@mtj.dyndns.org>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello, David.

On Fri, Feb 01, 2013 at 12:44:43PM -0500, David Teigland wrote:
> I already tried my own version of this, but used idr_for_each_entry a
> second time.  Unfortunately, the number it found and printed did not match
> recover_list_count.
> 
> warning: recover_list_count 566
> 
> It printed 304 ids:

Heh, that's really weird.  Maybe idr_get_next() is buggy above certain
number or at certain boundaries?  If you find something, please let me
know.  I'll see if I can reproduce it in some minimal way.

Thanks!

-- 
tejun