From: Ben Myers <bpm@sgi.com>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] XFS update for 3.2
Date: Thu, 29 Dec 2011 11:31:39 -0600 [thread overview]
Message-ID: <20111229173139.GL21646@sgi.com> (raw)
Hi Linus,
Please pull the following fixes for 3.2. Quoting Christoph Hellwig:
"These two small fixes fix issues with periodic metadata writeback and
sync not being able [to] write file size updates to disk in some cases."
These have not gone through -next because we have 3.3 work in the
oss/master branch right now, but they merged and built cleanly on
3.2-rc7. They have been tested thoroughly by Mark Tinguely and myself.
It is late in the cycle and I will submit them later for 3.2-stable if
you prefer.
Have a happy New Year!
Thanks,
Ben
The following changes since commit 371de6e4e0042adf4f9b54c414154f57414ddd37:
Keith Packard (1):
drm/i915: Disable RC6 on Sandybridge by default
are available in the git repository at:
git://oss.sgi.com/xfs/xfs for-linus
Christoph Hellwig (2):
xfs: log the inode in ->write_inode calls for kupdate
xfs: log all dirty inodes in xfs_fs_sync_fs
fs/xfs/xfs_super.c | 30 +++++-------------------------
fs/xfs/xfs_sync.c | 36 ++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_sync.h | 2 ++
3 files changed, 43 insertions(+), 25 deletions(-)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Ben Myers <bpm@sgi.com>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] XFS update for 3.2
Date: Thu, 29 Dec 2011 11:31:39 -0600 [thread overview]
Message-ID: <20111229173139.GL21646@sgi.com> (raw)
Hi Linus,
Please pull the following fixes for 3.2. Quoting Christoph Hellwig:
"These two small fixes fix issues with periodic metadata writeback and
sync not being able [to] write file size updates to disk in some cases."
These have not gone through -next because we have 3.3 work in the
oss/master branch right now, but they merged and built cleanly on
3.2-rc7. They have been tested thoroughly by Mark Tinguely and myself.
It is late in the cycle and I will submit them later for 3.2-stable if
you prefer.
Have a happy New Year!
Thanks,
Ben
The following changes since commit 371de6e4e0042adf4f9b54c414154f57414ddd37:
Keith Packard (1):
drm/i915: Disable RC6 on Sandybridge by default
are available in the git repository at:
git://oss.sgi.com/xfs/xfs for-linus
Christoph Hellwig (2):
xfs: log the inode in ->write_inode calls for kupdate
xfs: log all dirty inodes in xfs_fs_sync_fs
fs/xfs/xfs_super.c | 30 +++++-------------------------
fs/xfs/xfs_sync.c | 36 ++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_sync.h | 2 ++
3 files changed, 43 insertions(+), 25 deletions(-)
next reply other threads:[~2011-12-29 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 17:31 Ben Myers [this message]
2011-12-29 17:31 ` [GIT PULL] XFS update for 3.2 Ben Myers
-- strict thread matches above, loose matches on Subject: below --
2011-12-07 23:08 Ben Myers
2011-12-07 23:08 ` Ben Myers
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=20111229173139.GL21646@sgi.com \
--to=bpm@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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.