linux-kernel - Re: [PATCH v3 2/7] kbuild: list sub-directories in ./Kbuild

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKwvOdk8s5y_QQ7Gvp9E=LdxBtNnn4zkCzu40sHexxEZwwfO5w@mail.gmail.com>
Date:   Mon, 26 Sep 2022 14:06:36 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     kernel test robot <lkp@...el.com>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        kbuild-all@...ts.01.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>,
        Nathan Chancellor <nathan@...nel.org>,
        David Gow <davidgow@...gle.com>
Subject: Re: [PATCH v3 2/7] kbuild: list sub-directories in ./Kbuild

On Sat, Sep 24, 2022 at 5:29 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> On Sun, Sep 25, 2022 at 5:28 AM kernel test robot <lkp@...el.com> wrote:
> >
> > Hi Masahiro,
> >
> > I love your patch! Perhaps something to improve:
> >
> > [auto build test WARNING on masahiroy-kbuild/for-next]
> > [cannot apply to arm64/for-next/core gerg-m68knommu/for-next geert-m68k/for-next deller-parisc/for-next powerpc/next s390/features tip/x86/core linus/master v6.0-rc6 next-20220923]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch#_base_tree_information]
> >
> > url:    https://github.com/intel-lab-lkp/linux/commits/Masahiro-Yamada/kbuild-various-cleanups/20220925-022150
> > base:   https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next
> > config: um-x86_64_defconfig
> > compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
> > reproduce (this is a W=1 build):
> >         # https://github.com/intel-lab-lkp/linux/commit/d721cc5614aaa17b2965db04e9319d4ef5f7eaf7
> >         git remote add linux-review https://github.com/intel-lab-lkp/linux
> >         git fetch --no-tags linux-review Masahiro-Yamada/kbuild-various-cleanups/20220925-022150
> >         git checkout d721cc5614aaa17b2965db04e9319d4ef5f7eaf7
> >         # save the config file
> >         mkdir build_dir && cp config build_dir/.config
> >         make W=1 O=build_dir ARCH=um SUBARCH=x86_64 SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag where applicable
> > | Reported-by: kernel test robot <lkp@...el.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> /usr/bin/ld: warning: ./arch/x86/um/vdso/vdso.o: missing .note.GNU-stack section implies executable stack
> >    /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
> >    /usr/bin/ld: warning: .tmp_vmlinux.kallsyms1 has a LOAD segment with RWX permissions
> >    /usr/bin/ld: warning: .tmp_vmlinux.kallsyms1.o: missing .note.GNU-stack section implies executable stack
> >    /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
> >    /usr/bin/ld: warning: .tmp_vmlinux.kallsyms2 has a LOAD segment with RWX permissions
> >    /usr/bin/ld: warning: .tmp_vmlinux.kallsyms2.o: missing .note.GNU-stack section implies executable stack
> >    /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
> >    /usr/bin/ld: warning: vmlinux has a LOAD segment with RWX permissions

See also:
https://lore.kernel.org/lkml/20220921064855.2841607-1-davidgow@google.com/

> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://01.org/lkp
>
>
>
>
>
>
>
>
> My compiler is slightly different
> (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0), but
> I cannot reproduce it.
>
>
>
> Perhaps, 0day thought this is a new warning
> due to a slightly different path?
>
>
> [before]
> warning: arch/x86/um/vdso/vdso.o
>
> [after]
> warning: ./arch/x86/um/vdso/vdso.o
>
>
>
>
> --
> Best Regards
> Masahiro Yamada



-- 
Thanks,
~Nick Desaulniers