From: Greg KH <gregkh@linuxfoundation.org>
To: john.p.donnelly@oracle.com
Cc: bhe@redhat.com, 42.hyeyoo@gmail.com, David.Laight@aculab.com,
akpm@linux-foundation.org, bp@alien8.de, cl@linux.com,
david@redhat.com, hch@lst.de, iamjoonsoo.kim@lge.com,
m.szyprowski@samsung.com, penberg@kernel.org,
rientjes@google.com, robin.murphy@arm.com,
stable@vger.kernel.org, torvalds@linux-foundation.org,
vbabka@suse.cz
Subject: Re: FAILED: patch "[PATCH] dma/pool: create dma atomic pool only if dma zone has managed" failed to apply to 5.4-stable tree
Date: Mon, 24 Jan 2022 15:49:08 +0100 [thread overview]
Message-ID: <Ye68ZHq02pB59PF/@kroah.com> (raw)
In-Reply-To: <d9eec78f-e0e8-cc6d-ffe4-fbd31c8bb6a9@oracle.com>
On Mon, Jan 24, 2022 at 08:37:43AM -0600, john.p.donnelly@oracle.com wrote:
> On 1/23/22 8:29 AM, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.4-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>.
> >
> > thanks,
> >
> > greg k-h
>
>
> Hi,
>
>
> FWIIW :
>
> We picked up the suspect "Fixes" commit :
>
> 2020-10-01 | x86/kdump: Always reserve the low 1M when the crashkernel
> option is specified
>
> In an LTS update: 5.4.68, and I do not see the issue reported in the
> summary : "DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
> " , when a kdump is invoked. We test kdump quite regularly on a variety of
> platforms.
That commit was in 5.4.69, not .68. Or am I confused here?
that is why the 5.4 FAILED email was sent.
thanks,
greg k-h
prev parent reply other threads:[~2022-01-24 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 14:29 FAILED: patch "[PATCH] dma/pool: create dma atomic pool only if dma zone has managed" failed to apply to 5.4-stable tree gregkh
2022-01-24 14:37 ` john.p.donnelly
2022-01-24 14:49 ` 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=Ye68ZHq02pB59PF/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=42.hyeyoo@gmail.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.p.donnelly@oracle.com \
--cc=m.szyprowski@samsung.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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.