stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: "zhangyi (F)" <yi.zhang@huawei.com>,
	gregkh@linuxfoundation.org, stable@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 5.4 1/2] jbd2: move the clearing of b_modified flag to the journal_unmap_buffer()
Date: Tue, 18 Feb 2020 12:17:26 -0500	[thread overview]
Message-ID: <20200218171726.GA152025@mit.edu> (raw)
In-Reply-To: <20200218162752.GN1734@sasha-vm>

On Tue, Feb 18, 2020 at 11:27:52AM -0500, Sasha Levin wrote:
> On Tue, Feb 18, 2020 at 06:59:52PM +0800, zhangyi (F) wrote:
> > [ Upstream commit 6a66a7ded12baa6ebbb2e3e82f8cb91382814839 ]
> > 
> > There is no need to delay the clearing of b_modified flag to the
> > transaction committing time when unmapping the journalled buffer, so
> > just move it to the journal_unmap_buffer().
> > 
> > Link: https://lore.kernel.org/r/20200213063821.30455-2-yi.zhang@huawei.com
> > Reviewed-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
> > Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> > Cc: stable@kernel.org
> 
> I've queued all backports to their respective branches, thank you!

Many thanks to Yi Zhang for providing the backports!!

     	       	  	    	      - Ted

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 10:59 [PATCH 5.4 1/2] jbd2: move the clearing of b_modified flag to the journal_unmap_buffer() zhangyi (F)
2020-02-18 10:59 ` [PATCH 5.4 2/2] jbd2: do not clear the BH_Mapped flag when forgetting a metadata buffer zhangyi (F)
2020-02-18 16:27 ` [PATCH 5.4 1/2] jbd2: move the clearing of b_modified flag to the journal_unmap_buffer() Sasha Levin
2020-02-18 17:17   ` Theodore Y. Ts'o [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=20200218171726.GA152025@mit.edu \
    --to=tytso@mit.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yi.zhang@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 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).