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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Jun 2015 08:24:41 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Waldemar Brodkorb <wbx@...nadk.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	uClinux development list <uclinux-dev@...inux.org>
Subject: Re: m68k compile issue with 4.0.5

Hi Waldemar,

On Mon, Jun 15, 2015 at 10:23 PM, Waldemar Brodkorb <wbx@...nadk.org> wrote:
> I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k.
>
> With 4.0.4 everything is fine. With 4.0.5 I get following compile
> error:
>   adk-uclinux-gcc -Wp,-MD,mm/.nommu.o.d  -nostdinc -isystem
> /home/wbx/m68k/toolchain_qemu-m68k_uclibc-ng_m68k_nommu/usr/lib/gcc/m68k-openadk-uclinux-uclibc/4.9.2/include
> -I./arch/m68k/include -Iarch/m68k/include/generated/uapi
> -Iarch/m68k/include/generated  -Iinclude -I./arch/m68k/include/uapi
> -Iarch/m68k/include/generated/uapi -I./include/uapi
> -Iinclude/generated/uapi -include ./include/linux/kconfig.h
> -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> -fno-strict-aliasing -fno-common
> -Werror-implicit-function-declaration -Wno-format-security
> -std=gnu89 -mcpu=5208 -pipe -DUTS_SYSNAME=\"uClinux\" -D__uClinux__
> -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized
> --param=allow-store-data-races=0 -Wframe-larger-than=1024
> -fno-stack-protector -Wno-unused-but-set-variable
> -fomit-frame-pointer -fno-var-tracking-assignments
> -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
> -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes
> -Werror=date-time -DCC_HAVE_ASM_GOTO    -D"KBUILD_STR(s)=#s"
> -D"KBUILD_BASENAME=KBUILD_STR(nommu)"
> -D"KBUILD_MODNAME=KBUILD_STR(nommu)" -c -o mm/nommu.o mm/nommu.c
> mm/nommu.c: In function 'delete_vma':
> mm/nommu.c:861:3: error: implicit declaration of function 'vma_fput'
> [-Werror=implicit-function-declaration]
>    vma_fput(vma);
>    ^
> cc1: some warnings being treated as errors
>
> Any idea what change breaks the compile?

I tried a few m68knommu defconfigs, but can't reproduce it.

Is this a plain v4.0.5? I can't find the offending call to vma_fput().
"git grep vma_fput" tells me there's no "vma_fput" in the kernel sources?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ