linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	oe-kbuild-all@lists.linux.dev,
	 Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-stable 219/240] mm/memory.c:5410:41: error: implicit declaration of function 'vma_is_tcp'; did you mean 'vma_is_dax'?
Date: Mon, 14 Aug 2023 13:09:13 -0700	[thread overview]
Message-ID: <CAJuCfpGfsZtY5_Qi+Gew1z7Z0_Z_cAkrmxt+6cF6Sp-TR3A_kg@mail.gmail.com> (raw)
In-Reply-To: <20230814130623.90cf2bc8c625087ea616dd3c@linux-foundation.org>

On Mon, Aug 14, 2023 at 1:06 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Sun, 13 Aug 2023 16:17:21 +0800 kernel test robot <lkp@intel.com> wrote:
>
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-stable
> > head:   5fb2ea3111f4ecc6dc4891ce5b00f0217aae9a04
> > commit: 4aaa60dad4d1c96151dec51098aed866bb6e867d [219/240] mm: allow per-VMA locks on file-backed VMAs
> > config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20230813/202308131610.jF4ncWp6-lkp@intel.com/config)
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce: (https://download.01.org/0day-ci/archive/20230813/202308131610.jF4ncWp6-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202308131610.jF4ncWp6-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> >    In file included from include/linux/build_bug.h:5,
> >                     from include/linux/container_of.h:5,
> >                     from include/linux/list.h:5,
> >                     from include/linux/smp.h:12,
> >                     from include/linux/kernel_stat.h:5,
> >                     from mm/memory.c:42:
> >    mm/memory.c: In function 'lock_vma_under_rcu':
> > >> mm/memory.c:5410:41: error: implicit declaration of function 'vma_is_tcp'; did you mean 'vma_is_dax'? [-Werror=implicit-function-declaration]
> >     5410 |         if (unlikely(!vma->anon_vma && !vma_is_tcp(vma)))
> >          |                                         ^~~~~~~~~~
> >    include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
> >       77 | # define unlikely(x)    __builtin_expect(!!(x), 0)
> >          |                                             ^
> >    cc1: some warnings being treated as errors
> >
>
> This later gets accidentally fixed by Suren's "mm: handle userfaults
> under VMA lock".
>
> If Matthew can suggest a fix for this I can queue it close to "mm:
> allow per-VMA locks on file-backed VMAs" to minimize the size of the
> bisection hole?

I thought Matthew's suggestion here
https://lore.kernel.org/all/ZNerqcNS4EBJA%2F2v@casper.infradead.org/
would fix this. Dos it not?


  reply	other threads:[~2023-08-14 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13  8:17 kernel test robot
2023-08-14 19:47 ` Suren Baghdasaryan
2023-08-14 20:06 ` Andrew Morton
2023-08-14 20:09   ` Suren Baghdasaryan [this message]
2023-08-14 20:33     ` Suren Baghdasaryan
2023-08-14 20:41       ` Andrew Morton
2023-08-14 20:55         ` Suren Baghdasaryan

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=CAJuCfpGfsZtY5_Qi+Gew1z7Z0_Z_cAkrmxt+6cF6Sp-TR3A_kg@mail.gmail.com \
    --to=surenb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=willy@infradead.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