From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.7-rc4, part 2
Date: Sun, 3 May 2020 18:25:37 +0200 [thread overview]
Message-ID: <cover.1588522631.git.dsterba@suse.com> (raw)
Hi,
please pull a few more stability fixes, minor build warning fixes and
git url fixup. Thanks.
- fix partial loss of prealloc extent past i_size after fsync
- fix potential deadlock due to wrong transaction handle passing via
journal_info
- fix gcc 4.8 struct intialization warning
- update git URL in MAINTAINERS entry
----------------------------------------------------------------
The following changes since commit 1402d17dfd9657be0da8458b2079d03c2d61c86a:
btrfs: fix transaction leak in btrfs_recover_relocation (2020-04-23 17:24:56 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.7-rc3-tag
for you to fetch changes up to eb91db63a90d8f8e8768b82fcb2cae5f7198cf6b:
MAINTAINERS: btrfs: fix git repo URL (2020-05-03 18:13:18 +0200)
----------------------------------------------------------------
Arnd Bergmann (1):
btrfs: fix gcc-4.8 build warning for struct initializer
Eric Biggers (1):
MAINTAINERS: btrfs: fix git repo URL
Filipe Manana (1):
btrfs: fix partial loss of prealloc extent past i_size after fsync
Qu Wenruo (1):
btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info
MAINTAINERS | 2 +-
fs/btrfs/backref.c | 2 +-
fs/btrfs/transaction.c | 13 +++++++++++--
fs/btrfs/tree-log.c | 43 ++++++++++++++++++++++++++++++++++++++++---
4 files changed, 53 insertions(+), 7 deletions(-)
next reply other threads:[~2020-05-03 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 16:25 David Sterba [this message]
2020-05-03 18:35 ` [GIT PULL] Btrfs fixes for 5.7-rc4, part 2 pr-tracker-bot
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.1588522631.git.dsterba@suse.com \
--to=dsterba@suse.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 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.