All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: Jan Kara <jack@suse.cz>,
	linux-ext4@vger.kernel.org, luoshijie1@huawei.com,
	zhangxiaoxu5@huawei.com
Subject: Re: [PATCH v3 2/2] jbd2: do not clear the BH_Mapped flag when forgetting a metadata buffer
Date: Tue, 18 Feb 2020 12:04:42 -0500	[thread overview]
Message-ID: <20200218170442.GC147128@mit.edu> (raw)
In-Reply-To: <dcdd498d-68b4-360c-f0f1-3ee72ac0c1ad@huawei.com>

On Mon, Feb 17, 2020 at 06:38:23PM +0800, zhangyi (F) wrote:
> >> +			/*
> >> +			 * Block device buffers need to stay mapped all the
> >> +			 * time, so it is enough to clear buffer_jbddirty and
> >> +			 * buffer_freed bits. For the file mapping buffers (i.e.
> >> +			 * journalled data) we need to unmap buffer and clear
> >> +			 * more bits. We also need to be careful about the check
> >> +			 * because the data page mapping can get cleared under
> >> +			 * out hands, which alse need not to clear more bits
> > 			   ^^^ our    ^^^^ Maybe I'd rephrase this like:
> > 
> > ... under our hands. Note that if mapping == NULL, we don't need to make
> > buffer unmapped because the page is already detached from the mapping and
> > buffers cannot get reused.
> > 
> Thanks for your suggestion, Ted has already pushed this patch to upstream,
> I could write an appending patch to fix this.

Feel free to send a patch to fix up the comment if you like.

Thanks,

					- Ted

  reply	other threads:[~2020-02-18 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  6:38 [PATCH v3 0/2] jbd2: fix an oops problem zhangyi (F)
2020-02-13  6:38 ` [PATCH v3 1/2] jbd2: move the clearing of b_modified flag to the journal_unmap_buffer() zhangyi (F)
2020-02-13  6:38 ` [PATCH v3 2/2] jbd2: do not clear the BH_Mapped flag when forgetting a metadata buffer zhangyi (F)
2020-02-17  9:36   ` Jan Kara
2020-02-17 10:38     ` zhangyi (F)
2020-02-18 17:04       ` Theodore Y. Ts'o [this message]
2020-02-18  5:18   ` Ritesh Harjani
2020-02-18 16:46     ` Theodore Y. Ts'o

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=20200218170442.GC147128@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=luoshijie1@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=zhangxiaoxu5@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.