linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Glisse <jglisse@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <rdunlap@infradead.org>,
	akpm@linux-foundation.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
	broonie@kernel.org
Subject: Re: mmotm 2017-08-25-15-50 uploaded
Date: Mon, 28 Aug 2017 11:46:40 -0400 (EDT)	[thread overview]
Message-ID: <1201125186.4681340.1503935200216.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170828083157.GE17097@dhcp22.suse.cz>

> On Mon 28-08-17 18:27:05, Stephen Rothwell wrote:
> > Hi Michal,
> > 
> > On Mon, 28 Aug 2017 09:59:31 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> > >
> > > From 31d551dbcb1b7987a4cd07767c1e2805849b7a26 Mon Sep 17 00:00:00 2001
> > > From: Michal Hocko <mhocko@suse.com>
> > > Date: Mon, 28 Aug 2017 09:41:39 +0200
> > > Subject: [PATCH]
> > >  mm-hmm-struct-hmm-is-only-use-by-hmm-mirror-functionality-v2-fix
> > > 
> > > Compiler is complaining for allnoconfig
> > > 
> > > kernel/fork.c: In function 'mm_init':
> > > kernel/fork.c:814:2: error: implicit declaration of function
> > > 'hmm_mm_init' [-Werror=implicit-function-declaration]
> > >   hmm_mm_init(mm);
> > >   ^
> > > kernel/fork.c: In function '__mmdrop':
> > > kernel/fork.c:893:2: error: implicit declaration of function
> > > 'hmm_mm_destroy' [-Werror=implicit-function-declaration]
> > >   hmm_mm_destroy(mm);
> > > 
> > > Make sure that hmm_mm_init/hmm_mm_destroy empty stups are defined when
> > > CONFIG_HMM is disabled.
> > > 
> > > Signed-off-by: Michal Hocko <mhocko@suse.com>
> > > ---
> > >  include/linux/hmm.h | 7 +++----
> > >  1 file changed, 3 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/include/linux/hmm.h b/include/linux/hmm.h
> > > index 9583d9a15f9c..aeb94e682dda 100644
> > > --- a/include/linux/hmm.h
> > > +++ b/include/linux/hmm.h
> > > @@ -508,11 +508,10 @@ static inline void hmm_mm_init(struct mm_struct
> > > *mm)
> > >  {
> > >  	mm->hmm = NULL;
> > >  }
> > > -#else /* IS_ENABLED(CONFIG_HMM_MIRROR) */
> > > +#endif
> > > +
> > > +#else /* IS_ENABLED(CONFIG_HMM) */
> > >  static inline void hmm_mm_destroy(struct mm_struct *mm) {}
> > >  static inline void hmm_mm_init(struct mm_struct *mm) {}
> > > -#endif /* IS_ENABLED(CONFIG_HMM_MIRROR) */
> > > -
> > > -
> > >  #endif /* IS_ENABLED(CONFIG_HMM) */
> > >  #endif /* LINUX_HMM_H */
> > 
> > What happens when CONFIG_HMM is defined but CONFIG_HMM_MIRROR is not?
> > Or is that not possible (in which case why would we have
> > CONFIG_HMM_MIRROR)?
> 
> This is something to Jerome to answer but hmm_mm_init/hmm_mm_destroy are
> used regardless of the specific HMM configuration so an empty stub
> should be defined unconditionally AFAIU.

Sorry for the build issue i posted a patch on friday that i tested against
all combination :

https://lkml.org/lkml/2017/8/25/802

Michal is right this function needs to be defined no matter what but they
only need to be stub if HMM_MIRROR is not enabled.

The fix i posted has the correct logic. I missplaced the endif when i was
fixing Arnd build issue when HMM_MIRROR was not enabled but other HMM feature
were.

Jérôme

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2017-08-28 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 22:50 mmotm 2017-08-25-15-50 uploaded akpm
2017-08-25 23:50 ` Randy Dunlap
2017-08-28  7:59   ` Michal Hocko
2017-08-28  8:27     ` Stephen Rothwell
2017-08-28  8:31       ` Michal Hocko
2017-08-28 15:46         ` Jerome Glisse [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=1201125186.4681340.1503935200216.JavaMail.zimbra@redhat.com \
    --to=jglisse@redhat.com \
    --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@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).