From: Gavin Shan <gshan@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
kernel test robot <lkp@intel.com>,
linux-mm@kvack.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, shan.gavin@gmail.com
Subject: Re: [PATCH] mm/debug_vm_pgtable: Fix corrupted PG_arch_1 by set_pmd_at()
Date: Mon, 12 Jul 2021 18:24:25 +1000 [thread overview]
Message-ID: <4da06097-6f27-34b2-38b5-834b267ed62d@redhat.com> (raw)
In-Reply-To: <0a232c69-ae9f-8431-22c7-74513f87c018@arm.com>
On 7/12/21 1:21 PM, Anshuman Khandual wrote:
>
>
> On 7/8/21 6:05 AM, kernel test robot wrote:
>> Hi Gavin,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on linus/master]
>> [cannot apply to hnaz-linux-mm/master linux/master v5.13 next-20210707]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url: https://github.com/0day-ci/linux/commits/Gavin-Shan/mm-debug_vm_pgtable-Fix-corrupted-PG_arch_1-by-set_pmd_at/20210702-183310
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 3dbdb38e286903ec220aaf1fb29a8d94297da246
>> config: x86_64-allyesconfig (attached as .config)
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>> reproduce (this is a W=1 build):
>> # https://github.com/0day-ci/linux/commit/414db1c0feb54b545b3df56bc19ffff27580deb5
>> git remote add linux-review https://github.com/0day-ci/linux
>> git fetch --no-tags linux-review Gavin-Shan/mm-debug_vm_pgtable-Fix-corrupted-PG_arch_1-by-set_pmd_at/20210702-183310
>> git checkout 414db1c0feb54b545b3df56bc19ffff27580deb5
>> # save the attached .config to linux build tree
>> make W=1 ARCH=x86_64
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> In file included from arch/x86/include/asm/page.h:76,
>> from arch/x86/include/asm/thread_info.h:12,
>> from include/linux/thread_info.h:59,
>> from arch/x86/include/asm/preempt.h:7,
>> from include/linux/preempt.h:78,
>> from include/linux/spinlock.h:51,
>> from include/linux/mmzone.h:8,
>> from include/linux/gfp.h:6,
>> from mm/debug_vm_pgtable.c:13:
>> mm/debug_vm_pgtable.c: In function 'pud_advanced_tests':
>>>> include/asm-generic/memory_model.h:25:37: error: invalid operands to binary + (have 'struct page *' and 'struct page *')
>
>
> So this problem has been fixed in the other series (which now
> includes this patch) you have posted ?
>
Yes, Anshuman. Please ignore this one. The fix has been included into
the following series. The last patch [12/12] of that series fixes the
issue.
[PATCH 00/12] mm/debug_vm_pgtable: Enhancements
Thanks,
Gavin
prev parent reply other threads:[~2021-07-12 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 10:32 Gavin Shan
2021-07-02 18:10 ` kernel test robot
2021-07-03 0:30 ` Gavin Shan
2021-07-05 3:59 ` Anshuman Khandual
2021-07-06 5:09 ` Gavin Shan
2021-07-08 0:35 ` kernel test robot
2021-07-12 3:21 ` Anshuman Khandual
2021-07-12 8:24 ` Gavin Shan [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=4da06097-6f27-34b2-38b5-834b267ed62d@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.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