From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751759AbbHRAyo (ORCPT ); Mon, 17 Aug 2015 20:54:44 -0400 Received: from imap.thunk.org ([74.207.234.97]:35008 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750994AbbHRAym (ORCPT ); Mon, 17 Aug 2015 20:54:42 -0400 Date: Mon, 17 Aug 2015 20:54:37 -0400 From: "Theodore Ts'o" To: Felipe Balbi Cc: Christoph Hellwig , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, Greg KH , stable@vger.kernel.org, Nishanth Menon Subject: Re: Please revert 08439fec266c3cc5702953b4f54bdf5649357de0 Message-ID: <20150818005437.GA7535@thunk.org> Mail-Followup-To: Theodore Ts'o , Felipe Balbi , Christoph Hellwig , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, Greg KH , stable@vger.kernel.org, Nishanth Menon References: <20150817194502.GC16201@saruman.tx.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150817194502.GC16201@saruman.tx.rr.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 17, 2015 at 02:45:03PM -0500, Felipe Balbi wrote: > Hi Theodore, > > as you already know, commit 08439fec266c (ext4: remove > block_device_ejected) caused a regression for (at least) USB attached > storage devices. > > You provided a fix for the regression by reverting that commit in > b9e43f49f672 (Revert "ext4: remove block_device_ejected"). This > revert is, currently, on linux-next but broken commit is part of > v4.1-final and, thus, part of v4.1 LTS. > > Could you please mark your revert for v4.1+ stable ? If it's not too > late to get it in v4.2-final, that would be great, otherwise we a Cc > stable would suffice anyway. > > In summary, commit 08439fec266c needs to be reverted on both v4.1-stable > and v4.2. Already done. See the latest version of the dev branch. I noticed this morning that I needed to mark it for stable, and took care of it. - Ted