From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Potapenko <glider@google.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org, glider@google.com
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [patch 4/5] fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info()
Date: Thu, 28 May 2020 14:41:01 +0000 [thread overview]
Message-ID: <20200528144102.94E4B20814@mail.kernel.org> (raw)
In-Reply-To: <20200528052052.tLpI_z4pp%akpm@linux-foundation.org>
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.14, v5.4.42, v4.19.124, v4.14.181, v4.9.224, v4.4.224.
v5.6.14: Build OK!
v5.4.42: Build OK!
v4.19.124: Build OK!
v4.14.181: Failed to apply! Possible dependencies:
27e64b4be4b8 ("regset: Add support for dynamically sized regsets")
v4.9.224: Failed to apply! Possible dependencies:
27e64b4be4b8 ("regset: Add support for dynamically sized regsets")
v4.4.224: Failed to apply! Possible dependencies:
27e64b4be4b8 ("regset: Add support for dynamically sized regsets")
90954e7b9407 ("x86/coredump: Use pr_reg size, rather that TIF_IA32 flag")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-05-28 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200527222015.62ba8592af63dae12ab58ffe@linux-foundation.org>
2020-05-28 5:20 ` [patch 2/5] mm,thp: stop leaking unreleased file pages Andrew Morton
2020-05-28 5:20 ` [patch 3/5] mm: remove VM_BUG_ON(PageSlab()) from page_mapcount() Andrew Morton
2020-05-28 5:20 ` [patch 4/5] fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info() Andrew Morton
2020-05-28 14:41 ` Sasha Levin [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=20200528144102.94E4B20814@mail.kernel.org \
--to=sashal@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).