All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	stable-commits@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Patch "Revert "f2fs: fix to clear PG_checked flag in set_page_dirty()"" has been added to the 4.18-stable tree
Date: Sun, 11 Nov 2018 06:35:21 -0800	[thread overview]
Message-ID: <20181111143521.GA21748@kroah.com> (raw)
In-Reply-To: <CAD14+f1scE6Xuurjx+UrBwyrR7x6PG6w6kzoxWoVVUJ5QBJ8Ow@mail.gmail.com>

On Sun, Nov 11, 2018 at 06:13:14PM +0900, Ju Hyung Park wrote:
> Hi,
> 
> This bug was present only in 4.19.
> Is it still applicable to older branches?
> 
> Thanks.
> 
> On Sun, Nov 11, 2018, 12:26 PM <gregkh@linuxfoundation.org wrote:
> 
> >
> > This is a note to let you know that I've just added the patch titled
> >
> >     Revert "f2fs: fix to clear PG_checked flag in set_page_dirty()"
> >
> > to the 4.18-stable tree which can be found at:
> >
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> >      revert-f2fs-fix-to-clear-pg_checked-flag-in-set_page_dirty.patch
> > and it can be found in the queue-4.18 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From 164a63fa6b384e30ceb96ed80bc7dc3379bc0960 Mon Sep 17 00:00:00 2001
> > From: Jaegeuk Kim <jaegeuk@kernel.org>
> > Date: Tue, 16 Oct 2018 19:30:13 -0700
> > Subject: Revert "f2fs: fix to clear PG_checked flag in set_page_dirty()"
> >
> > From: Jaegeuk Kim <jaegeuk@kernel.org>
> >
> > commit 164a63fa6b384e30ceb96ed80bc7dc3379bc0960 upstream.
> >
> > This reverts commit 66110abc4c931f879d70e83e1281f891699364bf.

This commit was backported to 4.14.70 and 4.18.8 so it should also be
reverted there, right?  That is why I added it to those queues.

If this is incorrect, please let me know.

thanks,

greg k-h

      parent reply	other threads:[~2018-11-11 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <154190097675163@kroah.com>
     [not found] ` <CAD14+f1scE6Xuurjx+UrBwyrR7x6PG6w6kzoxWoVVUJ5QBJ8Ow@mail.gmail.com>
2018-11-11  9:14   ` Patch "Revert "f2fs: fix to clear PG_checked flag in set_page_dirty()"" has been added to the 4.18-stable tree Ju Hyung Park
2018-11-11 14:35   ` Greg KH [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=20181111143521.GA21748@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=qkrwngud825@gmail.com \
    --cc=stable-commits@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 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.