From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: rppt@kernel.org
Cc: riel@surriel.com, kernel-team@fb.com,
Ram Pai <linuxram@us.ibm.com>,
linux-kernel@vger.kernel.org, guro@fb.com, linux-mm@kvack.org,
Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
iamjoonsoo.kim@lge.com, mhocko@kernel.org,
linuxppc-dev@lists.ozlabs.org, akpm@linux-foundation.org,
Thiago Jung Bauermann <bauerman@linux.ibm.com>
Subject: Re: [PATCH v2 2/2] memblock: do not start bottom-up allocations with kernel_end
Date: Fri, 22 Jan 2021 01:37:14 -0300 [thread overview]
Message-ID: <20210122043714.266075-1-bauerman@linux.ibm.com> (raw)
In-Reply-To: <20201220064959.GB392325@kernel.org>
Mike Rapoport <rppt@kernel.org> writes:
> > Signed-off-by: Roman Gushchin <guro@fb.com>
>
> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
I've seen a couple of spurious triggers of the WARN_ONCE() removed by this
patch. This happens on some ppc64le bare metal (powernv) server machines with
CONFIG_SWIOTLB=y and crashkernel=4G, as described in a candidate patch I posted
to solve this issue in a different way:
https://lore.kernel.org/linuxppc-dev/20201218062103.76102-1-bauerman@linux.ibm.com/
Since this patch solves that problem, is it possible to include it in the next
feasible v5.11-rcX, with the following tag?
Fixes: 8fabc623238e ("powerpc: Ensure that swiotlb buffer is allocated from low memory")
This is because reverting the commit above also solves the problem on the
machines where I've seen this issue.
--
Thiago Jung Bauermann
IBM Linux Technology Center
next parent reply other threads:[~2021-01-22 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201220064959.GB392325@kernel.org>
2021-01-22 4:37 ` Thiago Jung Bauermann [this message]
2021-01-24 2:09 ` [PATCH v2 2/2] memblock: do not start bottom-up allocations with kernel_end Andrew Morton
2021-01-24 7:34 ` Mike Rapoport
2021-01-26 0:30 ` Thiago Jung Bauermann
2021-02-08 23:58 ` Thiago Jung Bauermann
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=20210122043714.266075-1-bauerman@linux.ibm.com \
--to=bauerman@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@fb.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mhocko@kernel.org \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=sathnaga@linux.vnet.ibm.com \
/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