From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:59705 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751039AbeEUIcB (ORCPT ); Mon, 21 May 2018 04:32:01 -0400 Date: Mon, 21 May 2018 10:31:44 +0200 From: Greg KH To: Nikolay Borisov Cc: stable@vger.kernel.org Subject: Re: Please include following patches to 4.4/4.9/4.14 Message-ID: <20180521083144.GA7485@kroah.com> References: <2daf3525-7a2a-6d8c-0151-a8cd767cff0a@suse.com> <20180521082404.GC28845@kroah.com> <715b0867-ad0a-40bd-8d97-b1048d63424e@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <715b0867-ad0a-40bd-8d97-b1048d63424e@suse.com> Sender: stable-owner@vger.kernel.org List-ID: On Mon, May 21, 2018 at 11:27:37AM +0300, Nikolay Borisov wrote: > > > On 21.05.2018 11:24, Greg KH wrote: > > On Mon, May 21, 2018 at 10:18:00AM +0300, Nikolay Borisov wrote: > >> Hello Greg, > >> > >> Here are trivial backports for upstream commit, which is tagged as stable: > >> > >> 02a3307aa9c2 ("btrfs: fix reading stale metadata blocks after degraded > >> raid1 mounts") > > > > What about 4.16? > > I only provided patches for LTS releases. In any case, the code in > question hasn't changed recently so the 4.14 backport should apply to 4.16. I don't want someone moving from a 4.14-lts release to 4.16 to hit a regression, that would be foolish :) Anyway, thanks, I'll take the 4.14 backport. greg k-h