Re: [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 8 Nov 2020 09:35:38 -0800
- Cc: Ingo Molnar <mingo@xxxxxxxxxx>, x86-ml <x86@xxxxxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, "Paul E. McKenney" <paulmck@xxxxxxxxxx>, Will Deacon <will.deacon@xxxxxxx>
- In-reply-to: <20201108092333.GA13870@zn.tnic>
- References: <160476203869.11244.7869849163897430965.tip-bot2@tip-bot2> <20201107160444.GB30275@zn.tnic> <20201108090521.GA108695@gmail.com> <20201108092333.GA13870@zn.tnic>
On Sun, Nov 8, 2020 at 1:23 AM Borislav Petkov <bp@xxxxxxxxx> 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
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]