From: Greg KH <greg@kroah.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: stable@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"John Ogness" <john.ogness@linutronix.de>,
"Mel Gorman" <mgorman@techsingularity.net>,
"Michal Hocko" <mhocko@suse.com>,
"Patrick Daly" <quic_pdaly@quicinc.com>,
"Petr Mladek" <pmladek@suse.com>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: [PATCH 4.14.y] mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock
Date: Mon, 8 May 2023 08:56:20 +0200 [thread overview]
Message-ID: <2023050828-asleep-semicolon-240e@gregkh> (raw)
In-Reply-To: <20230507145629.4250-1-penguin-kernel@I-love.SAKURA.ne.jp>
On Sun, May 07, 2023 at 11:56:29PM +0900, Tetsuo Handa wrote:
> commit 1007843a91909a4995ee78a538f62d8665705b66 upstream.
For obvious reasons, we can't just apply this to 4.14.y. Please provide
fixes for all other stable trees as well so that you do not have a
regression when updating to a newer kernel.
I'll drop this from my review queue for now and wait for all of the
backported versions.
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-08 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:05 FAILED: patch "[PATCH] mm/page_alloc: fix potential deadlock on zonelist_update_seq" failed to apply to 4.14-stable tree gregkh
2023-05-07 14:56 ` [PATCH 4.14.y] mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock Tetsuo Handa
2023-05-08 6:56 ` Greg KH [this message]
2023-05-08 10:06 ` Tetsuo Handa
2023-05-09 8:55 ` Petr Mladek
2023-05-14 4:41 ` [PATCH 4.14.y] printk: declare printk_deferred_{enter,safe}() in include/linux/printk.h Tetsuo Handa
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=2023050828-asleep-semicolon-240e@gregkh \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=quic_pdaly@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stable@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