From: Greg KH <gregkh@linuxfoundation.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: keescook@chromium.org, willy@infradead.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] coredump: Use the vma snapshot in fill_files_note" failed to apply to 5.17-stable tree
Date: Tue, 5 Apr 2022 08:36:55 +0200 [thread overview]
Message-ID: <YkvjhziWC7iLShZ7@kroah.com> (raw)
In-Reply-To: <YkvikRzy2ahCbGV6@kroah.com>
On Tue, Apr 05, 2022 at 08:32:49AM +0200, Greg KH wrote:
> On Mon, Apr 04, 2022 at 11:00:19AM -0500, Eric W. Biederman wrote:
> > <gregkh@linuxfoundation.org> writes:
> >
> > > The patch below does not apply to the 5.17-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> >
> > I believe it requires backporting these first.
> >
> > commit 84158b7f6a06 ("coredump: Also dump first pages of non-executable ELF libraries")
> > commit 95c5436a4883 ("coredump: Snapshot the vmas in do_coredump")
> > commit 49c1866348f3 ("coredump: Remove the WARN_ON in dump_vma_snapshot")
> >
> > The first is a more interesting bug fix from Jann Horn.
> > The other two are prerequisite cleanup-patches.
>
> Thanks, that worked!
Nope, also had to add 9ec7d3230717 ("coredump/elf: Pass coredump_params into fill_note_info")
next prev parent reply other threads:[~2022-04-05 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 11:36 FAILED: patch "[PATCH] coredump: Use the vma snapshot in fill_files_note" failed to apply to 5.17-stable tree gregkh
2022-04-04 16:00 ` Eric W. Biederman
2022-04-05 6:32 ` Greg KH
2022-04-05 6:36 ` Greg KH [this message]
2022-04-05 14:24 ` Eric W. Biederman
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=YkvjhziWC7iLShZ7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).