Messages in this thread | | | Date | Sun, 7 Mar 2004 17:15:50 +0100 | From | Olaf Hering <> | Subject | linux-2.5 cset 1.1654.1.2 xfs filemap_flush() unresolved |
| |
filemap_flush() is not an exported symbol, at least not in my tree.
> ChangeSet > 1.1654.1.2 04/03/06 14:47:10 nathans@sgi.com +1 -0 > [XFS] Fix out-of-space deadlock when flushing delalloc data with pages locked under write. > > SGI Modid: xfs-linux:xfs-kern:167948a > > fs/xfs/linux/xfs_super.c > 1.70 04/03/06 14:46:51 nathans@sgi.com +1 -1 > [XFS] Fix out-of-space deadlock when flushing delalloc data with pages locked under write. > > ......................................................................... > # This is a BitKeeper generated patch for the following project: > # Project Name: Linux kernel tree > # This patch format is intended for GNU patch command version 2.5 or higher. > # This patch includes the following deltas: > # ChangeSet 1.1654.1.1 -> 1.1654.1.2 > # fs/xfs/linux/xfs_super.c 1.69 -> 1.70 > # > # The following is the BitKeeper ChangeSet Log > # -------------------------------------------- > # 04/03/06 nathans@sgi.com 1.1654.1.2 > # [XFS] Fix out-of-space deadlock when flushing delalloc data with pages locked under write. > # > # SGI Modid: xfs-linux:xfs-kern:167948a > # -------------------------------------------- > # > diff -Nru a/fs/xfs/linux/xfs_super.c b/fs/xfs/linux/xfs_super.c > --- a/fs/xfs/linux/xfs_super.c Sun Mar 7 06:25:54 2004 > +++ b/fs/xfs/linux/xfs_super.c Sun Mar 7 06:25:54 2004 > @@ -247,7 +247,7 @@ > { > struct inode *inode = LINVFS_GET_IP(XFS_ITOV(ip)); > > - filemap_fdatawrite(inode->i_mapping); > + filemap_flush(inode->i_mapping); > } > > void > ......................................................................... > # vim: syntax=diff >
-- USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |