linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: dingdinghua <dingdinghua85@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH]JBD2/JBD: race condition while writing updates to journal
Date: Sun, 21 Jun 2009 20:09:15 -0400	[thread overview]
Message-ID: <20090622000915.GA6464@mit.edu> (raw)
In-Reply-To: <4A3E5E2B.4020106@gmail.com>

On Mon, Jun 22, 2009 at 12:22:03AM +0800, dingdinghua wrote:
> 
> At committing phase, we call jbd2_journal_write_metadata_buffer to
> prepare log block's buffer_head, in this function, new_bh->b_data is set
> to b_frozen_data or bh_in->b_data. We call "jbd_unlock_bh_state(bh_in)"
> too early, since at this point , we haven't file bh_in to BJ_shadow list,
> and we may set new_bh->b_data to bh_in->b_data, at this time, another
> thread may call get write access of bh_in, modify bh_in->b_data and
> dirty it. So , if new_bh->b_data is set to bh_in->b_data, the committing
> transaction may flush the newly modified buffer content to disk,
> preserve work done in jbd2_journal_get_write_access is useless. jbd also
> has this problem.
> 
> here is the patch based on kernel version 2.6.30:

This patch is completely whitespace damaged.  Could you resend it
using a mail user agent that doesn't damage patches, please?    Thanks!!

      	     	  	     	     	    - Ted

  reply	other threads:[~2009-06-22  0:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-21 16:22 [PATCH]JBD2/JBD: race condition while writing updates to journal dingdinghua
2009-06-22  0:09 ` Theodore Tso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-22  8:05 dingdinghua
2009-07-15 14:47 ` Jan Kara
2009-07-15 18:13   ` Jan Kara
2009-07-17  1:36     ` Theodore Tso
2009-07-18 19:14       ` 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=20090622000915.GA6464@mit.edu \
    --to=tytso@mit.edu \
    --cc=dingdinghua85@gmail.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).