linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 丁定华 <dingdinghua85@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: Re: journal forget may introduce buffer aliasing problem?
Date: Wed, 27 Jan 2010 13:58:54 +0800	[thread overview]
Message-ID: <7bb361261001262158q37fe060br93c751c1152c5738@mail.gmail.com> (raw)
In-Reply-To: <7bb361261001261944v7b5d698bn9da51d1f418c1594@mail.gmail.com>

Oops, I haven't seen unmap_underlying_metadata code in __block_prepare_write
so just forget this mail, sorry.

2010/1/27 丁定华 <dingdinghua85@gmail.com>:
> Hi all:
>       The following is my analysis(if wrong, please point it out),
> may be I can send a patch out if it's a bug.
>       If buffer_head belongs to comitting transaction,
> jbd2_journal_forget do nothing except discard it from running
> transaction. So this buffer will happily be inserted
> into committing_transaction's checkpoint list and do write-back work,
> then this buffer may be re-used as data-block, then there are two
> buffer_heads maps to the same block, buffer aliasing occurs, and we
> can't control the writeback order of the two buffer heads, fs may be
> inconsistent.
>      The same thing will happen if buffer_head doesn't belongs to
> running or committing transaction, but lays in checkpoint list.
>
> --
> 丁定华
>



-- 
丁定华
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-01-27  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27  3:44 journal forget may introduce buffer aliasing problem? 丁定华
2010-01-27  5:58 ` 丁定华 [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=7bb361261001262158q37fe060br93c751c1152c5738@mail.gmail.com \
    --to=dingdinghua85@gmail.com \
    --cc=jack@suse.cz \
    --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).