From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/3] Btrfs: inode cache fixes
Date: Mon, 16 Dec 2013 15:25:32 +0800 [thread overview]
Message-ID: <1387178735-30832-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.
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 | 3 +++
fs/btrfs/inode-map.c | 25 +++++++++++++++++++++----
fs/btrfs/inode-map.h | 1 +
fs/btrfs/root-tree.c | 3 +++
4 files changed, 28 insertions(+), 4 deletions(-)
--
1.8.2.1
next reply other threads:[~2013-12-16 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 7:25 Liu Bo [this message]
2013-12-16 7:25 ` [PATCH v2 1/3] Btrfs: avoid building inode cache repeatly Liu Bo
2013-12-16 9:04 ` Miao Xie
2013-12-16 10:26 ` Liu Bo
2013-12-16 10:54 ` Miao Xie
2013-12-16 15:09 ` Chris Mason
2013-12-16 7:25 ` [PATCH v2 2/3] Btrfs: don't build inode cache for orphan root Liu Bo
2013-12-16 7:25 ` [PATCH v2 3/3] Btrfs: fix EEXIST error when creating new file in subvolume/snapshot 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=1387178735-30832-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 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.