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: <CAK7LNASzxcicBPM5OkScnwHPef_7X=oiuO_0xCH3f55ACYZEWw@mail.gmail.com>
Date:   Fri, 9 Aug 2019 13:44:19 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Heiko Carstens <heiko.carstens@...ibm.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Aug 8

Hi Heiko, Stephen,

On Fri, Aug 9, 2019 at 7:53 AM Heiko Carstens <heiko.carstens@...ibm.com> wrote:
>
> On Thu, Aug 08, 2019 at 06:17:39PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190807:
> >
> > I reverted a commit from the kbuild-current tree by request.
>
> Hello Masahiro,
>
> it looks like there is (another?) bug in kbuild. With your patch
>
> commit 421a15c167b2d1f43f287da5b75ef2704650640b (refs/bisect/bad)
> Author: Masahiro Yamada <yamada.masahiro@...ionext.com>
> Date:   Fri Jul 26 11:17:47 2019 +0900
>
>     kbuild: clean-up subdir-ym computation
>
>     The intermediate variables __subdir-{y,m} are unneeded.
>
>     Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
>
> the file modules.builtin starts to miss a lot of entries when building
> the kernel tree. Reverting that patch on top of linux-next 20190808
> restores the old behaviour.
>
> This is the diff I get without and with the above commit (s390 with
> defconfig):
>
> --- modules.builtin.ok  2019-08-09 00:39:58.148624485 +0200
> +++ modules.builtin     2019-08-09 00:40:07.878637541 +0200


You are right. This commit is bad.


Stephen, could you revert this commit for today's linux-next ?


BTW, I had dropped this commit from my branch (with another reason),
but I forgot to push it to the public place...


-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ