linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d
Date: Sun, 23 May 2021 16:34:08 +0800	[thread overview]
Message-ID: <4fa6822e-fe6d-9cc0-a094-844a70e24219@intel.com> (raw)
In-Reply-To: <20210522112947.5a5116759db138f32f36d151@linux-foundation.org>



On 5/23/2021 2:29 AM, Andrew Morton wrote:
> On Sat, 22 May 2021 23:05:26 +0800 kernel test robot <lkp@intel.com> wrote:
> 
>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> branch HEAD: 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d  Add linux-next specific files for 20210521
>>
>> mm/mremap.c:306:8: warning: variable 'pud' set but not used [-Wunused-but-set-variable]
>>
>> ...
>>
>> |-- arm64-randconfig-r014-20210521
>> |   |-- kernel-kallsyms.c:warning:no-previous-prototype-for-kallsyms_lookup_buildid
>> |   `-- mm-mremap.c:warning:variable-pud-set-but-not-used
>>
>> ...
>>
>> |-- i386-allmodconfig
>> |   |-- drivers-net-wireless-ath-ath10k-htt_rx.c:warning:variable-more_frags-set-but-not-used
>> |   |-- kernel-kallsyms.c:warning:no-previous-prototype-for-kallsyms_lookup_buildid
>> |   `-- mm-mremap.c:warning:variable-pud-set-but-not-used
>>
> 
> I can't reproduce this.  move_normal_pud() does
> 
> 	pud_populate(mm, new_pud, (pmd_t *)pud_page_vaddr(pud));
> 
> and I can't see a version of pud_page_vaddr() which doesn't reference its
> argument.
> 
> Maybe it was fixed since this release of next.
> 

Hi Andrew,

The original report can be found at 
https://lore.kernel.org/linux-mm/202105180059.7qbrqAhs-lkp@intel.com/

Best Regards,
Rong Chen


      reply	other threads:[~2021-05-23  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 15:05 kernel test robot
2021-05-22 18:29 ` Andrew Morton
2021-05-23  8:34   ` Chen, Rong A [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=4fa6822e-fe6d-9cc0-a094-844a70e24219@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.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