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] [day] [month] [year] [list]
Message-ID: <CAK7LNAS5nvQDYD8jqazng2_CwuuZMGE2FyLFF73iW1_Vp6DWgw@mail.gmail.com>
Date:   Fri, 28 Oct 2022 01:31:29 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     linux-kbuild@...r.kernel.org, Jiri Slaby <jirislaby@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>,
        Nicolas Schier <nicolas@...sle.eu>,
        linux-kernel@...r.kernel.org,
        Nathan Chancellor <nathan@...nel.org>,
        clang-built-linux <llvm@...ts.linux.dev>, eng.stk@...o.pt
Subject: Re: [PATCH] kbuild: fix 'Broken pipe' message for AR=gcc-ar

On Tue, Oct 25, 2022 at 4:15 AM Nick Desaulniers
<ndesaulniers@...gle.com> wrote:
>
> On Sun, Oct 23, 2022 at 12:53 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
> >
> > Since commit 321648455061 ("kbuild: use obj-y instead extra-y for
> > objects placed at the head"), 'make AR=gcc-ar' shows the following
> > message:
> >
> >   /usr/bin/ar terminated with signal 13 [Broken pipe]
>
> Not just AR=gcc-ar, but also AR=llvm-ar:
>
> error: write on a pipe with no reader
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/1651
> Reported-by: Nathan Chancellor <nathan@...nel.org>
> Tested-by: Nick Desaulniers <ndesaulniers@...gle.com>



Thank you.

I updated the commit description, and sent v2.

https://lore.kernel.org/linux-kbuild/20221027162839.410720-1-masahiroy@kernel.org/T/#u


> Note that due to
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8017ce50641c303b9b5d96f3c10229ecfd770a70
> we should send a backport to stable like:
> https://github.com/engstk/op8/commit/6f2688e3eb4ec06b276e541640d4f06364b68442


Maybe, we can backport 8017ce50641c30 itself,
but I am not sure if it is cleanly applicable.



-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ