From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, sashal@kernel.org
Cc: stable@vger.kernel.org,
Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
Qu Wenruo <wqu@suse.com>, David Sterba <dsterba@suse.com>,
Filipe Manana <fdmanana@suse.com>, Pavel Machek <pavel@denx.de>,
Nikolay Borisov <nborisov@suse.com>
Subject: missing btrfs fixes for 4.14-stable, 4.9-stable and 4.4-stable
Date: Mon, 21 Dec 2020 16:03:16 +0000 [thread overview]
Message-ID: <20201221160316.ftczjtpmva6rtw74@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hi Greg, Sasha,
Few missing btrfs fixes for 4.14-stable, 4.9-stable and 4.4-stable.
Only one of them was marked for stable but looks like they should be.
6f7de19ed3d4 ("btrfs: quota: Set rescan progress to (u64)-1 if we hit
last leaf")
665d4953cde6 ("btrfs: scrub: Don't use inode page cache in
scrub_handle_errored_block()")
9f7fec0ba891 ("Btrfs: fix selftests failure due to uninitialized i_mode
in test inodes")
881a3a11c2b8 ("btrfs: fix return value mixup in btrfs_get_extent")
--
Regards
Sudip
[-- Attachment #2: btrfs_4.14-stable.mbox --]
[-- Type: application/mbox, Size: 5479 bytes --]
[-- Attachment #3: btrfs_4.9-stable.mbox --]
[-- Type: application/mbox, Size: 10814 bytes --]
[-- Attachment #4: btrfs_4.4-stable.mbox --]
[-- Type: application/mbox, Size: 10669 bytes --]
next reply other threads:[~2020-12-21 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 16:03 Sudip Mukherjee [this message]
2020-12-28 9:14 ` missing btrfs fixes for 4.14-stable, 4.9-stable and 4.4-stable Greg Kroah-Hartman
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=20201221160316.ftczjtpmva6rtw74@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=misono.tomohiro@jp.fujitsu.com \
--cc=nborisov@suse.com \
--cc=pavel@denx.de \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wqu@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox