From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] Btrfs: fixes for inode cache (-o inode_cache)
Date: Thu, 4 Jul 2019 16:24:00 +0100 [thread overview]
Message-ID: <20190704152400.20614-1-fdmanana@kernel.org> (raw)
From: Filipe Manana <fdmanana@suse.com>
Just a small set of fixes for the inode cache feature, mostly hangs due to
missing wakeups or incomplete error handling, as well as an inode block
reserve leak when hitting ENOSPC.
Filipe Manana (5):
Btrfs: fix hang when loading existing inode cache off disk
Btrfs: fix inode cache block reserve leak on failure to allocate data
space
Btrfs: fix inode cache waiters hanging on failure to start caching
thread
Btrfs: fix inode cache waiters hanging on path allocation failure
Btrfs: wake up inode cache waiters sooner to reduce waiting time
fs/btrfs/inode-map.c | 30 ++++++++++++++++++++++++------
1 file changed, 24 insertions(+), 6 deletions(-)
--
2.11.0
next reply other threads:[~2019-07-04 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 15:24 fdmanana [this message]
2019-07-31 17:39 ` [PATCH 0/5] Btrfs: fixes for inode cache (-o inode_cache) 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=20190704152400.20614-1-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox