From: Rong Chen <rong.a.chen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Cc: Yang Shi <shy828301@gmail.com>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org, Zi Yan <ziy@nvidia.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] Re: mm/migrate.c:1406:5: warning: stack frame size of 2096 bytes in function 'migrate_pages'
Date: Wed, 2 Jun 2021 12:58:53 +0800 [thread overview]
Message-ID: <d61e9459-2d90-340c-a4f8-9cfc05498c35@intel.com> (raw)
In-Reply-To: <20210531151412.4dad38dd703119cdd33ca395@linux-foundation.org>
On 6/1/21 6:14 AM, Andrew Morton wrote:
> On Sun, 30 May 2021 17:46:48 +0800 kernel test robot <lkp@intel.com> wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: b90e90f40b4ff23c753126008bf4713a42353af6
>> commit: dd4ae78a21fc05d91d841e499dddd057ad64a4df mm: migrate: simplify the logic for handling permanent failure
> migrate_pages() isn't a good place to be using lots of stack.
>
> Am I correct in assuming that this is a bisection result?
Hi Andrew,
I have confirmed the bisection is good.
>
> I don't immediately see why dd4ae78a21fc05d91d would be the main cause
> of this.
>
Hi Clang Team, could you share some experience about this kind of warning?
Best Regards,
Rong Chen
prev parent reply other threads:[~2021-06-02 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 9:46 kernel test robot
2021-05-31 22:14 ` Andrew Morton
2021-06-02 4:58 ` Rong Chen [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=d61e9459-2d90-340c-a4f8-9cfc05498c35@intel.com \
--to=rong.a.chen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=shy828301@gmail.com \
--cc=ziy@nvidia.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