linux-kernel - Re: stable 4.16.5 hmm build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 Apr 2018 09:30:04 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Михаил Носов <drdeimosnn@...il.com>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>,
        Jérôme Glisse <jglisse@...hat.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: stable 4.16.5 hmm build error

On Fri, Apr 27, 2018 at 02:19:24AM +0300, Михаил Носов wrote:
> Oh. Yes. Tag v4.16.5 without commit
> 9d8a463a7016e9e5578a561588a18acef139919c.
> It's in v4.17-rc1/2.
> Thank you.

That patch does not apply to the stable trees.  I'm also confused by the
lack of "real" git commit ids that are being referred to here, that
commit refers to one that is not valid.

> 2018-04-27 0:52 GMT+03:00 Randy Dunlap <rdunlap@...radead.org>:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=199515
> >
> > kernel/fork.o: In function `__mmdrop':
> > /kernel/build_kernel/linux-4.16.4/kernel/fork.c:600: undefined reference
> > to `hmm_mm_destroy'

What .config is creating this?  I have not seen any kbuild reports of
this in the past.

> >
> > "It is also reproduced in linux-4.16.5"
> >
> >
> > There have been a few attempts to fix this build error.  The kernel
> > mainline
> > repo seems to have it fixed, but it looks to me like Arnd's latest patch
> > (9d8a463a7016e: "mm/hmm: fix header file if/else/endif maze, again")
> > was mis-merged to 4.16.5 stable.
> >
> > Please take a look.  Do you already have a fixup for this?

thanks,

greg k-h