From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
clm@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 4.14-rc4
Date: Fri, 6 Oct 2017 17:34:36 +0200 [thread overview]
Message-ID: <cover.1507303159.git.dsterba@suse.com> (raw)
Hi,
we have two more fixes for bugs introduced in 4.13. The sector_t problem with
32bit architecture and !LBDAF config seems serious but the number of affected
deployments is hopefully low. The clashing status bits could lead to a
confusing in-memory state of the whole-filesystem operations if used with the
quota override sysfs knob.
Please pull, thanks.
The following changes since commit 8c6c592831a09a28428448e68fb08c6bbb8b9b8b:
btrfs: log csums for all modified extents (2017-09-26 14:54:16 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.14-rc4
for you to fetch changes up to 69ad59767d094752c23c0fc180a79532fde073d0:
Btrfs: fix overlap of fs_info::flags values (2017-10-04 16:44:18 +0200)
----------------------------------------------------------------
Goffredo Baroncelli (1):
btrfs: avoid overflow when sector_t is 32 bit
Tsutomu Itoh (1):
Btrfs: fix overlap of fs_info::flags values
fs/btrfs/ctree.h | 2 +-
fs/btrfs/extent_io.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2017-10-06 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:34 David Sterba [this message]
2017-10-06 22:25 ` [GIT PULL] Btrfs fixes for 4.14-rc4 Tomasz Kłoczko
2017-10-06 23:23 ` Liu Bo
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.1507303159.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).