All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: dsterba@suse.com, anand.jain@oracle.com,
	johannes.thumshirn@wdc.com, lists@colorremedies.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] btrfs: print message when tree-log replay starts" failed to apply to 4.9-stable tree
Date: Tue, 18 Feb 2020 11:41:25 -0500	[thread overview]
Message-ID: <20200218164125.GP1734@sasha-vm> (raw)
In-Reply-To: <1581966528133167@kroah.com>

On Mon, Feb 17, 2020 at 08:08:48PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From e8294f2f6aa6208ed0923aa6d70cea3be178309a Mon Sep 17 00:00:00 2001
>From: David Sterba <dsterba@suse.com>
>Date: Wed, 5 Feb 2020 17:12:16 +0100
>Subject: [PATCH] btrfs: print message when tree-log replay starts
>
>There's no logged information about tree-log replay although this is
>something that points to previous unclean unmount. Other filesystems
>report that as well.
>
>Suggested-by: Chris Murphy <lists@colorremedies.com>
>CC: stable@vger.kernel.org # 4.4+
>Reviewed-by: Anand Jain <anand.jain@oracle.com>
>Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>Signed-off-by: David Sterba <dsterba@suse.com>

Context changes due to 0b246afa62b0 ("btrfs: root->fs_info cleanup, add
fs_info convenience variables"). Cleaned up and queued on 4.9 and 4.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2020-02-18 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 19:08 FAILED: patch "[PATCH] btrfs: print message when tree-log replay starts" failed to apply to 4.9-stable tree gregkh
2020-02-18 16:41 ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200218164125.GP1734@sasha-vm \
    --to=sashal@kernel.org \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.thumshirn@wdc.com \
    --cc=lists@colorremedies.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.