This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".
The branch, for-linus has been updated
c141b29 xfs: only issues a cache flush on unmount if barriers are enabled
7d46be4 xfs: prevent lockdep false positive in xfs_iget_cache_miss
ff392c4 xfs: prevent kernel crash due to corrupted inode log format
from 27e88bf6af7d42adf790f7b2ed7d65475f191cf2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c141b2928fe20396a9ecdec85526e4b66ae96c90
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Mar 3 14:48:37 2009 -0500
xfs: only issues a cache flush on unmount if barriers are enabled
Currently we unconditionally issue a flush from xfs_free_buftarg, but
since 2.6.29-rc1 this gives a warning in the style of
end_request: I/O error, dev vdb, sector 0
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
Signed-off-by: Felix Blyakher <felixb@xxxxxxx>
commit 7d46be4a25fdfb503c20bad60a618adebfe2ac5c
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Mar 3 14:48:35 2009 -0500
xfs: prevent lockdep false positive in xfs_iget_cache_miss
The inode can't be locked by anyone else as we just created it a few
lines above and it's not been added to any lookup data structure yet.
So use a trylock that must succeed to get around the lockdep warnings.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reported-by: Alexander Beregalov <a.beregalov@xxxxxxxxx>
Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
Reviewed-by: Felix Blyakher <felixb@xxxxxxx>
Signed-off-by: Felix Blyakher <felixb@xxxxxxx>
commit ff392c497b43ddedbab5627b53928a654cc5486e
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Mar 3 14:48:36 2009 -0500
xfs: prevent kernel crash due to corrupted inode log format
Andras Korn reported an oops on log replay causes by a corrupted
xfs_inode_log_format_t passing a 0 size to kmem_zalloc. This patch handles
to small or too large numbers of log regions gracefully by rejecting the
log replay with a useful error message.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reported-by: Andras Korn <korn-sgi.com@xxxxxxxxxxxxxxxxxxxxxx>
Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
Signed-off-by: Felix Blyakher <felixb@xxxxxxx>
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/linux-2.6/xfs_buf.c | 12 ++++++++++--
fs/xfs/linux-2.6/xfs_buf.h | 2 +-
fs/xfs/linux-2.6/xfs_super.c | 10 +++++-----
fs/xfs/xfs_iget.c | 15 ++++++++++-----
fs/xfs/xfs_log_recover.c | 17 +++++++++++++----
5 files changed, 39 insertions(+), 17 deletions(-)
hooks/post-receive
--
XFS development tree
|