[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181211221935.GC6478@redhat.com>
Date: Tue, 11 Dec 2018 17:19:35 -0500
From: Jerome Glisse <jglisse@...hat.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Michal Hocko <mhocko@...e.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/mmu_notifier: fix mmu_notifier_range_init warning
On Tue, Dec 11, 2018 at 10:53:03PM +0100, Arnd Bergmann wrote:
> On Tue, Dec 11, 2018 at 10:43 PM David Rientjes <rientjes@...gle.com> wrote:
> >
> > On Tue, 11 Dec 2018, Jerome Glisse wrote:
>
> >
> > Hmm, strange that Arnd's build failure is only reporting about an unused
> > variable instead of MMU_NOTIFY_CLEAR being undefined :/
> >
> > I think this should be done so that anybody using
> > mmu_notifier_range_init() doesn't need to worry about the implications of
> > *any* unused formal parameter as a result of how the #define is formed:
>
> Your patch below is more or less what I tried at first, and that resulted
> in another build failure for
>
> mm/hugetlb.c: mmu_notifier_range_init(&range, mm, start, end,
> MMU_NOTIFY_CLEAR);
> mm/hugetlb.c- adjust_range_if_pmd_sharing_possible(vma,
> &range.start, &range.end);
>
> where range.end refers to a nonexisting member of range.
>
> Arnd
I will post a v3 with htmldoc fix and build warning fix incorporated.
Cheers,
Jérôme
Powered by blists - more mailing lists