public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"reiserfs-dev@namesys.com" <reiserfs-dev@namesys.com>
Subject: Re: [reiserfs-dev] [patch 5/15] reiserfs locking fix
Date: 21 May 2002 08:29:05 -0400	[thread overview]
Message-ID: <1021984145.22608.173.camel@tiny> (raw)
In-Reply-To: <3CE7FF5A.FEDD69CB@zip.com.au>

On Sun, 2002-05-19 at 15:39, Andrew Morton wrote:
> 
> 
> reiserfs is using b_inode_buffers and fsync_buffers_list() for
> attaching dependent buffers to its journal.  For writeout prior to
> commit.
> 
> This worked OK when a global lock was used everywhere, but the locking
> is currently incorrect - try_to_free_buffers() is taking a different
> lock when detaching buffers from their "foreign" inode.  So list_head
> corruption could occur on SMP.

Thanks Andrew, this is working for me here.

-chris



      reply	other threads:[~2002-05-21 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 19:39 [patch 5/15] reiserfs locking fix Andrew Morton
2002-05-21 12:29 ` Chris Mason [this message]

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=1021984145.22608.173.camel@tiny \
    --to=mason@suse.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.com \
    --cc=torvalds@transmeta.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