From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: [PULL] Btrfs, misc for 4.6
Date: Mon, 21 Mar 2016 19:42:09 +0100 [thread overview]
Message-ID: <cover.1458585064.git.dsterba@suse.com> (raw)
Hi,
a few low-risk patches that appeared after I sent my main pull for 4.6. I think
they still apply to 4.6, the freezer patches help the livepatch to clean up the
mis-use of the freezer API, the rest makes sure we don't miss an error during
writing checksums.
I've removed Liu Bo's patch fixing the writeback_index, IMO needs moe review
and can be merged in some later rc.
----------------------------------------------------------------
The following changes since commit 5e33a2bd7ca7fa687fb0965869196eea6815d1f3:
Btrfs: do not collect ordered extents when logging that inode exists (2016-03-01 08:23:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris-4.6
for you to fetch changes up to 45147cbef21305b512a5b263e9e52f832a0df7b2:
btrfs: transaction_kthread() is not freezable (2016-03-21 19:02:34 +0100)
----------------------------------------------------------------
Alex Lyakas (2):
btrfs: csum_tree_block: return proper errno value
btrfs: do not write corrupted metadata blocks to disk
Jiri Kosina (2):
btrfs: cleaner_kthread() doesn't need explicit freeze
btrfs: transaction_kthread() is not freezable
fs/btrfs/disk-io.c | 45 +++++++++++++++++++++++++--------------------
1 file changed, 25 insertions(+), 20 deletions(-)
next reply other threads:[~2016-03-21 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 18:42 David Sterba [this message]
2016-03-22 10:03 ` [PULL] Btrfs, misc for 4.6 David Sterba
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=cover.1458585064.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=linux-btrfs@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.