public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Chris Mason <mason@suse.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] buffer_insert_list should use list_add_tail
Date: Fri, 20 Jun 2003 09:11:17 +1000	[thread overview]
Message-ID: <20030619231117.GB722@frodo> (raw)
In-Reply-To: <1056028538.6757.94.camel@tiny.suse.com>

On Thu, Jun 19, 2003 at 09:15:39AM -0400, Chris Mason wrote:
> Hello all,
> 
> buffer_insert_list puts buffers onto the head of bh->b_inode_buffers,
> which means that on fsync we are writing things out in reverse order.  I
> think we either want this patch, or we want to walk the list in reverse
> in fsync_buffers_list
> 
> (this has not been well tested, but I can't think of any problems it
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> would cause)


hi Chris,

We noticed this too and Christoph made this change in the
2.4 XFS tree a little while ago - let me check dates - ah,
9th May.  So, fair bit of testing here and we've not seen
any issues from this change either (we'd also like to see
it merged).

thanks.


> 
> -chris
> 
> --- linux.marcelo/fs/buffer.c	Thu Jun 19 09:09:28 2003
> +++ linux/fs/buffer.c	Thu Jun 19 09:04:17 2003
> @@ -591,7 +604,7 @@
>  	if (buffer_attached(bh))
>  		list_del(&bh->b_inode_buffers);
>  	set_buffer_attached(bh);
> -	list_add(&bh->b_inode_buffers, list);
> +	list_add_tail(&bh->b_inode_buffers, list);
>  	spin_unlock(&lru_list_lock);
>  }
>  
> 
> 
> 
> -
> 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/

-- 
Nathan

  reply	other threads:[~2003-06-19 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 13:15 [PATCH] buffer_insert_list should use list_add_tail Chris Mason
2003-06-19 23:11 ` Nathan Scott [this message]
2003-06-21  8:48   ` Christoph Hellwig

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=20030619231117.GB722@frodo \
    --to=nathans@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.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