From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756843AbcLNVKR (ORCPT ); Wed, 14 Dec 2016 16:10:17 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:35610 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753250AbcLNVKP (ORCPT ); Wed, 14 Dec 2016 16:10:15 -0500 Date: Wed, 14 Dec 2016 13:09:35 -0800 From: Brian Norris To: Karl Beldan Cc: Boris Brezillon , Richard Weinberger , "linux-mtd@lists.infradead.org" , David Woodhouse , "linux-kernel@vger.kernel.org" , Daniel Walter , Stable Subject: Re: [PATCH v2 01/46] mtdpart: Propagate _get/put_device() Message-ID: <20161214210935.GA135941@google.com> References: <984fd8eb53b742bd46e7b42605ae4e0ceaf5ba08.1474450295.git.dwalter@sigma-star.at> <20160921121531.7786ee9b@bbrezillon> <20160928201611.GB142302@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 14, 2016 at 07:24:46PM +0000, Karl Beldan wrote: > On Wed, Sep 28, 2016 at 8:16 PM, Brian Norris > wrote: > > On Wed, Sep 21, 2016 at 12:15:31PM +0200, Boris Brezillon wrote: > >> On Wed, 21 Sep 2016 11:43:56 +0200 > >> Daniel Walter wrote: > >> > >> > From: Richard Weinberger > >> > > >> > If the master device has callbacks for _get/put_device() > >> > and this MTD has slaves a get_mtd_device() call on paritions > >> > will never issue the registered callbacks. > >> > Fix this by propagating _get/put_device() down. > >> > >> Brian, can we have this one queued for 4.9? I can't take it in my tree > >> if you want, but it's probably better if it's in the mtd tree. > > > > Applied this patch to l2-mtd.git > > > > I think this should also go into -stable. Why? Do you have real use cases that are broken by this? I understand this is a problem, but I'm curious on how this satisfies the stable rules. Also, note that this isn't a regression; it's been broken forever and apparently no one noticed. IMO that raises the bar a bit (but not impossibly so) for -stable. Anyway, if we decide to do this, you'll also want to include the git hash and applicable kernel versions, per Option 2 [1]. Brian [1] Documentation/stable_kernel_rules.txt.