linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Linux Btrfs" <linux-btrfs@vger.kernel.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fix
Date: Mon, 03 Oct 2011 14:25:12 -0400	[thread overview]
Message-ID: <1317666169-sup-1696@shiny> (raw)

Hi everyone,

Josef found a btrfs bug that can lead us to loop trying to fault in
pages during btrfs_file_write.  I've pushed the fix out to the btrfs git
tree.  Linus, please pull from the btrfs-3.0 branch:

git://github.com/chrismason/linux.git btrfs-3.0


Josef Bacik (1) commits (+16/-8):
    Btrfs: force a page fault if we have a shorty copy on a page boundary

Total: (1) commits (+16/-8)

 fs/btrfs/file.c |   24 ++++++++++++++++--------
 1 files changed, 16 insertions(+), 8 deletions(-)

             reply	other threads:[~2011-10-03 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 18:25 Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-30 16:48 [GIT PULL] Btrfs fix Chris Mason
2015-02-06 20:16 Chris Mason
2015-05-08 21:32 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=1317666169-sup-1696@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).