Date: Tue, 4 Aug 2015 21:56:31 +0200
From: Pavel Machek <pavel@ucw.cz>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Tejun Heo <tj@kernel.org>, Dan Williams <dan.j.williams@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is devm_* broken ?
Message-ID: <20150804195631.GB28564@amd>
References: <1503739.gVWYM3p8QD@avalon>
 <1643821.fnPPMYQxCt@avalon>
 <20150728152225.GA454@mtj.duckdns.org>
 <3561824.rKlMSGlkdL@avalon>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3561824.rKlMSGlkdL@avalon>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1522
Lines: 33

On Tue 2015-07-28 20:05:49, Laurent Pinchart wrote:
> On Tuesday 28 July 2015 11:22:25 Tejun Heo wrote:
> > On Tue, Jul 28, 2015 at 05:16:16PM +0300, Laurent Pinchart wrote:
> > > Using devm_kzalloc() in such a way has value though, and reverting drivers
> > > to the pre-devm memory allocation code would make error handling and
> > > cleanup code paths more complex again. Should we introduce a managed
> > > allocator for that purpose that would have a lifespan explicitly handled
> > > by drivers ?
> >
> > I don't know.  Sure, we can have memory allocations which are tied to
> > open file; however, the distinction between that and regular devm
> > resources, which can't linger on no matter what, would be subtle and
> > confusing.  IMHO, a better approach would be implmenting generic
> > revoke feature and sever open files on driver detach so that
> > everything can be shutdown then.
> 
> Sounds like a topic for the kernel summit :-) I'll send a proposal.

Hmm. But that means that devm_ everything is broken for 6 months or
so, right?

Does it mean we should stop taking new devm_ conversions at the very
least?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/