From: Chris Mason <chris.mason@oracle.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fixes
Date: Mon, 19 Sep 2011 19:57:08 -0400 [thread overview]
Message-ID: <1316476217-sup-4802@shiny> (raw)
Hi everyone,
The for-linus branch of the btrfs tree on github:
Head commit: a66e7cc626f42de6c745963fe0d807518fa49d39
git://github.com/chrismason/linux.git for-linus
Has the following fixes. for-linus is against rc6, since some of these
are regression fixes for earlier 3.1 btrfs commits. The most important
of the bunch is Josef's dentry fix, which avoids enoents if we race with
multiple procs hitting on the same inode. This bug is btrfs-specific,
it came in with his optimization to cache the inode location during
readdir.
Li Zefan (3) commits (+9/-5):
Btrfs: don't make a file partly checksummed through file clone (+5/-0)
Btrfs: don't change inode flag of the dest clone file (+0/-1)
Btrfs: fix pages truncation in btrfs_ioctl_clone() (+4/-4)
Josef Bacik (1) commits (+11/-2):
Btrfs: only clear the need lookup flag after the dentry is setup
Jeff Liu (1) commits (+7/-2):
BTRFS: Fix lseek return value for error
Hidetoshi Seto (1) commits (+3/-2):
btrfs: fix d_off in the first dirent
Total: (6) commits (+30/-11)
fs/btrfs/file.c | 9 +++++++--
fs/btrfs/inode.c | 18 ++++++++++++++----
fs/btrfs/ioctl.c | 14 +++++++++-----
3 files changed, 30 insertions(+), 11 deletions(-)
next reply other threads:[~2011-09-19 23:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 23:57 Chris Mason [this message]
2011-09-20 16:19 ` [GIT PULL] Btrfs fixes Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 Chris Mason
2015-11-05 11:20 fdmanana
2015-11-05 14:59 ` Chris Mason
2015-05-15 19:11 Chris Mason
2015-05-01 14:08 Chris Mason
2015-04-26 13:18 Chris Mason
2015-03-20 16:55 Chris Mason
2015-01-23 18:49 Chris Mason
2015-01-08 18:28 Chris Mason
2014-11-01 16:05 Chris Mason
2014-09-19 19:47 Chris Mason
2013-03-17 12:34 Chris Mason
2013-02-07 0:13 Chris Mason
2013-02-07 0:09 Chris Mason
2013-01-23 0:48 Chris Mason
2013-01-23 1:28 ` Liu Bo
2013-01-23 1:40 ` Chris Mason
2013-01-24 21:52 ` Chris Mason
2013-01-25 3:13 ` Linus Torvalds
2012-10-26 14:19 Chris Mason
2012-05-06 13:35 Chris Mason
2012-04-28 12:27 Chris Mason
2012-01-27 16:34 Chris Mason
2012-01-27 16:31 Chris Mason
2011-12-23 17:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-16 18:29 ` nobody
2011-12-08 19:24 Chris Mason
2011-11-22 1:30 Chris Mason
2011-11-11 21:40 Chris Mason
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2010-04-12 20:00 [GIT PULL] Btrfs fixes Chris Mason
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=1316476217-sup-4802@shiny \
--to=chris.mason@oracle.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).