Bug 199515 - undefined reference to `hmm_mm_destroy'
Summary: undefined reference to `hmm_mm_destroy'
Status: RESOLVED CODE_FIX
Alias: None
Product: Process Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: process_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-25 23:12 UTC by Mikhail Nosov
Modified: 2018-05-02 17:23 UTC (History)
1 user (show)

See Also:
Kernel Version: linux-4.16.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments
kernel config (212.55 KB, text/x-mpsub)
2018-04-25 23:12 UTC, Mikhail Nosov
Details

Description Mikhail Nosov 2018-04-25 23:12:48 UTC
Created attachment 275579 [details]
kernel config

Build latest stable kernel from https:////cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.4.tar.xz
with cmd make -j6 deb-pkg end with error in fork.c

OS: Ubuntu 16.04
Kernel: 4.16.3 builded with same config
Built in docker container.

Log:
  CC [M]  drivers/watchdog/wm8350_wdt.o
  CC [M]  drivers/watchdog/max63xx_wdt.o
  CC [M]  drivers/watchdog/softdog.o
  CC [M]  drivers/watchdog/menf21bmc_wdt.o
  CC [M]  drivers/watchdog/rave-sp-wdt.o
  AR      drivers/watchdog/watchdog.o
  AR      drivers/watchdog/built-in.o
  AR      drivers/built-in.o
  GEN     .version
  CHK     include/generated/compile.h
  AR      built-in.o
  LD      vmlinux.o
  MODPOST vmlinux.o
kernel/fork.o: In function `__mmdrop':
/kernel/build_kernel/linux-4.16.4/kernel/fork.c:600: undefined reference to `hmm_mm_destroy'
Makefile:1041: recipe for target 'vmlinux' failed
make[2]: *** [vmlinux] Error 1
scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1398: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2
Comment 1 Mikhail Nosov 2018-04-25 23:17:08 UTC
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
Comment 2 Mikhail Nosov 2018-04-26 10:27:38 UTC
It is also reproduced in linux-4.16.5
Comment 3 Mikhail Nosov 2018-05-02 17:23:24 UTC
Fixed in linux-4.16.6

Note You need to log in before you can comment on or make changes to this bug.