The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: nathans@sgi.com
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: linux-2.5 cset 1.1654.1.2  xfs filemap_flush() unresolved
Date: Sun, 7 Mar 2004 17:15:50 +0100	[thread overview]
Message-ID: <20040307161550.GA2812@suse.de> (raw)
In-Reply-To: <20040307052556.4BABC468E4@mandarine.suse.de>



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

       reply	other threads:[~2004-03-07 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040307052556.4BABC468E4@mandarine.suse.de>
2004-03-07 16:15 ` Olaf Hering [this message]
2004-03-08  8:52   ` linux-2.5 cset 1.1654.1.2 xfs filemap_flush() unresolved Nathan Scott

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=20040307161550.GA2812@suse.de \
    --to=olh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox