linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	SeongJae Park <sj@kernel.org>
Subject: Re: mmotm 2021-10-13-19-52 uploaded (mm/damon/vaddr.c)
Date: Thu, 14 Oct 2021 11:18:37 +0000	[thread overview]
Message-ID: <20211014111837.5504-1-sj@kernel.org> (raw)
In-Reply-To: <2232228f-573b-ac19-1cb0-88690fdf6177@infradead.org>

On Wed, 13 Oct 2021 22:15:05 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:

> [-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
> 
> On 10/13/21 7:52 PM, akpm@linux-foundation.org wrote:
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > https://www.ozlabs.org/~akpm/mmotm/
> > 
> > This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> > more than once a week.
> > 
> > You will need quilt to apply these patches to the latest Linus release (5.x
> > or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> > https://ozlabs.org/~akpm/mmotm/series
> > 
> > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> > followed by the base kernel version against which this patch series is to
> > be applied.
> 
> on i386:
> 
> In file included from ../include/linux/mm.h:33:0,
>                   from ../include/linux/kallsyms.h:13,
>                   from ../include/linux/bpf.h:20,
>                   from ../include/linux/bpf-cgroup.h:5,
>                   from ../include/linux/cgroup-defs.h:22,
>                   from ../include/linux/cgroup.h:28,
>                   from ../include/linux/hugetlb.h:9,
>                   from ../mm/damon/vaddr.c:11:
> ../mm/damon/vaddr.c: In function ‘damon_mkold_pmd_entry’:
> ../include/linux/pgtable.h:97:12: error: implicit declaration of function ‘kmap_atomic’; did you mean ‘mcopy_atomic’? [-Werror=implicit-function-declaration]
>    ((pte_t *)kmap_atomic(pmd_page(*(dir))) +  \
>              ^
> ../include/linux/mm.h:2376:17: note: in expansion of macro ‘pte_offset_map’
>    pte_t *__pte = pte_offset_map(pmd, address); \
>                   ^~~~~~~~~~~~~~
> ../mm/damon/vaddr.c:387:8: note: in expansion of macro ‘pte_offset_map_lock’
>    pte = pte_offset_map_lock(walk->mm, pmd, addr, &ptl);
>          ^~~~~~~~~~~~~~~~~~~
> ../include/linux/pgtable.h:99:24: error: implicit declaration of function ‘kunmap_atomic’; did you mean ‘in_atomic’? [-Werror=implicit-function-declaration]
>   #define pte_unmap(pte) kunmap_atomic((pte))
>                          ^
> ../include/linux/mm.h:2384:2: note: in expansion of macro ‘pte_unmap’
>    pte_unmap(pte);     \
>    ^~~~~~~~~
> ../mm/damon/vaddr.c:392:2: note: in expansion of macro ‘pte_unmap_unlock’
>    pte_unmap_unlock(pte, ptl);
>    ^~~~~~~~~~~~~~~~
> 
> 
> Full randconfig file is attached.

Thank you for this report!

I sent a fix:
https://lore.kernel.org/linux-mm/20211014110848.5204-1-sj@kernel.org/

This was found and fixed by Andrew before, but I made this mistake again... :'(
To not repeat this again, I added a test for this case in DAMON correctness
tests: https://github.com/awslabs/damon-tests/commit/b3d1513ad16a


Thanks,
SJ

> 
> -- 
> ~Randy


      reply	other threads:[~2021-10-14 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  2:52 mmotm 2021-10-13-19-52 uploaded akpm
2021-10-14  5:15 ` mmotm 2021-10-13-19-52 uploaded (mm/damon/vaddr.c) Randy Dunlap
2021-10-14 11:18   ` SeongJae Park [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=20211014111837.5504-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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