[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170622185837.GD18600@htj.duckdns.org>
Date: Thu, 22 Jun 2017 14:58:37 -0400
From: Tejun Heo <tj@...nel.org>
To: Matthew Wilcox <mawilcox@...rosoft.com>,
Chris Wilson <chris@...is-wilson.co.uk>
Cc: David Airlie <airlied@...ux.ie>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org, sachinp <sachinp@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Subject: Re: [next-20170609] WARNING: CPU: 3 PID: 71167 at lib/idr.c:157
idr_replace
On Thu, Jun 22, 2017 at 12:31:35AM +0100, Chris Wilson wrote:
> Quoting Tejun Heo (2017-06-13 14:58:49)
> > Cc'ing David Airlie.
> >
> > This is from drm driver calling in idr_replace() w/ a negative id.
> > Probably a silly bug in error handling path?
>
> No, this is the validation of an invalid userspace handle. The drm ABI
> for handles is supposed to be a full u32 range with 0 reserved for an
> invalid handle (constrained by the idr_alloc ofc). The WARN was
> introduced by 0a835c4f090a.
Matthew, did idr lost some of its range while being reimplemented
using radix tree?
Thanks.
--
tejun
Powered by blists - more mailing lists