Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220924181915.3251186-3-masahiroy@kernel.org>
 <202209250350.jJ8vDPnH-lkp@intel.com> <CAK7LNAT9rrSZ2NfTB2G_YZUwE48NbDHPJbM4NbjtwSGWA1YR4Q@mail.gmail.com>
 <CAKwvOdk8s5y_QQ7Gvp9E=LdxBtNnn4zkCzu40sHexxEZwwfO5w@mail.gmail.com>
In-Reply-To: <CAKwvOdk8s5y_QQ7Gvp9E=LdxBtNnn4zkCzu40sHexxEZwwfO5w@mail.gmail.com>
From:   Masahiro Yamada <masahiroy@kernel.org>
Date:   Wed, 28 Sep 2022 17:32:09 +0900
Message-ID: <CAK7LNAQWrOYZws4U5GpmzyAOWab2wdZi1mgK4wouEqH3KeAQiA@mail.gmail.com>
Subject: Re: [PATCH v3 2/7] kbuild: list sub-directories in ./Kbuild
To:     Nick Desaulniers <ndesaulniers@google.com>
Cc:     kernel test robot <lkp@intel.com>,
        Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
        kbuild-all@lists.01.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-arch <linux-arch@vger.kernel.org>,
        Nathan Chancellor <nathan@kernel.org>,
        David Gow <davidgow@google.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Sep 27, 2022 at 6:06 AM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> On Sat, Sep 24, 2022 at 5:29 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
> >
> > On Sun, Sep 25, 2022 at 5:28 AM kernel test robot <lkp@intel.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@intel.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/


Ah, thank you.
My binutils version is 2.38, and
that is why I was not able to reproduce the issue.


With binutils 2.39, now I see the warnings in the mainline kernel.
My patch is not the root cause.


-- 
Best Regards
Masahiro Yamada