From: Mark Fasheh <mark.fasheh@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] JBD checkpoint cleanup strikes back
Date: Tue, 2 May 2006 16:47:22 -0700 [thread overview]
Message-ID: <20060502234721.GA5768@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20060502184646.GK14703@atrey.karlin.mff.cuni.cz>
On Tue, May 02, 2006 at 08:46:46PM +0200, Jan Kara wrote:
> The patch was already in 2.6.16-rc3 but was dropped because of
> problems with OCFS2. I've now tracked down the problem - OCFS2 relies on
> the fact that buffer does not have journal_head if it is not on any
> transaction's list. It assumes that if the buffer has buffer_jbd set,
> then it is journaled and hence the node has uptodate data in the
> buffer. My patch broke that assumption as in one path I forgot to call
> journal_remove_journal_head() and hence I was leaving behind some
> buffers not attached to any transaction but with journal_head. Now that
> leak is fixed and OCFS2 seems to work fine also with my patch.
Ahh, ok that makes sense and it definitely sounds like the type of thing
that would cause OCFS2 to pick up stale data.
> Andrew, could you please put the patch into -mm? Thanks.
Without commenting any further on the patch, I can definitely offer up some
more testing on my end should Andrew decide to pick this up.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2006-05-02 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 18:46 [PATCH] JBD checkpoint cleanup strikes back Jan Kara
2006-05-02 23:47 ` Mark Fasheh [this message]
2006-05-03 10:25 ` Jan Kara
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=20060502234721.GA5768@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=akpm@osdl.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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