From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] Btrfs: inode cache fixes
Date: Fri, 13 Dec 2013 17:16:20 +0800 [thread overview]
Message-ID: <1386926183-18325-1-git-send-email-bo.li.liu@oracle.com> (raw)
The first patch aims to fix the bug of repeatly building inode cache.
The next two patches fix problems with the first one applied.
For better review, I decided to have three patches instead of folding them into
one.
Liu Bo (3):
Btrfs: avoid building inode cache repeatly
Btrfs: don't build inode cache for orphan root
Btrfs: fix EEXIST error when creating new file in subvolume/snapshot
fs/btrfs/disk-io.c | 9 +++++----
fs/btrfs/inode-map.c | 21 +++++++++++++++++----
2 files changed, 22 insertions(+), 8 deletions(-)
--
1.8.2.1
next reply other threads:[~2013-12-13 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 9:16 Liu Bo [this message]
2013-12-13 9:16 ` [PATCH 1/3] Btrfs: avoid building inode cache repeatly Liu Bo
2013-12-13 9:38 ` Miao Xie
2013-12-13 9:16 ` [PATCH 2/3] Btrfs: don't build inode cache for orphan root Liu Bo
2013-12-13 9:43 ` Miao Xie
2013-12-13 9:16 ` [PATCH 3/3] Btrfs: fix EEXIST error when creating new file in subvolume/snapshot Liu Bo
2013-12-13 9:46 ` Miao Xie
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=1386926183-18325-1-git-send-email-bo.li.liu@oracle.com \
--to=bo.li.liu@oracle.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 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).