linux-kernel - Re: [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's

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]

Date:   Sun, 8 Nov 2020 09:35:38 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Ingo Molnar <mingo@...nel.org>, x86-ml <x86@...nel.org>,
        linux-tip-commits@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Will Deacon <will.deacon@....com>
Subject: Re: [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's

On Sun, Nov 8, 2020 at 1:23 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Sun, Nov 08, 2020 at 10:05:21AM +0100, Ingo Molnar wrote:
> > So that mode change to executable was intentional, as mentioned in the
> > changelog.
>
> Yeah, I thought we don't make them executable in the tree but I guess we
> do, at least most of them, from looking at git ls-files *.sh output.

We do try mark scripts executable, but you may have been misled by the
fact that we then try to avoid _depending_ on that during the build.

That's mostly because some people still use old workflows with
patches, and the executable bit will be lost if you apply a patch
without the proper git tools.

(I think we've also had cases where people were developing on no-exec
filesystems etc).

So while we try to mark scripts executable, we then actually generally
execute them using an explicit interpreter invocation anyway (ie using

  $(CONFIG_SHELL) "some-script-path"

or similar).

              Linus