From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: stable@vger.kernel.org, John Ogness <john.ogness@linutronix.de>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 5.10.y] printk: declare printk_deferred_{enter,safe}() in include/linux/printk.h
Date: Mon, 15 May 2023 18:06:06 +0200 [thread overview]
Message-ID: <2023051501-mockup-override-c57e@gregkh> (raw)
In-Reply-To: <7f66845a-d27f-f1c8-fccf-91cd3be95024@I-love.SAKURA.ne.jp>
On Mon, May 15, 2023 at 10:11:33PM +0900, Tetsuo Handa wrote:
> On 2023/05/15 21:56, Greg Kroah-Hartman wrote:
> > On Sun, May 14, 2023 at 01:41:27PM +0900, Tetsuo Handa wrote:
> >> commit 85e3e7fbbb720b9897fba9a99659e31cbd1c082e upstream.
> >>
> >> [This patch implements subset of original commit 85e3e7fbbb72 ("printk:
> >> remove NMI tracking") where commit 1007843a9190 ("mm/page_alloc: fix
> >> potential deadlock on zonelist_update_seq seqlock") depends on, for
> >> commit 3d36424b3b58 ("mm/page_alloc: fix race condition between
> >> build_all_zonelists and page allocation") was backported to stable.]
> >
> > All now queued up, thanks.
>
> Thank you. Then, please also queue original "[PATCH] mm/page_alloc: fix potential
> deadlock on zonelist_update_seq" (Message ID listed below) to stable kernels.
>
> <2023042446-gills-morality-d566@gregkh>
> <2023042449-wobbling-putdown-13ea@gregkh>
> <2023042452-stopper-engross-e9da@gregkh>
> <2023042455-skinless-muzzle-1c50@gregkh>
>
Now done, thanks.
greg k-h
prev parent reply other threads:[~2023-05-15 16:06 UTC|newest]
Thread overview: 5+ 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 5.10-stable tree gregkh
2023-05-14 4:41 ` [PATCH 5.10.y] printk: declare printk_deferred_{enter,safe}() in include/linux/printk.h Tetsuo Handa
2023-05-15 12:56 ` Greg Kroah-Hartman
2023-05-15 13:11 ` Tetsuo Handa
2023-05-15 16:06 ` Greg Kroah-Hartman [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=2023051501-mockup-override-c57e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--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