All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for -rc5
Date: Fri, 12 Apr 2019 17:05:15 +0100	[thread overview]
Message-ID: <20190412160515.GH31037@fuggles.cambridge.arm.com> (raw)

Hi Linus,

Please pull these three arm64 fixes for -rc5. The main thing is a fix to
our FUTEX_WAKE_OP implementation which was unbelievably broken, but did
actually work for the one scenario that GLIBC used to use.

Summary in the tag.

Thanks,

Will

--->8

The following changes since commit 15ade5d2e7775667cf191cf2f94327a4889f8b9d:

  Linux 5.1-rc4 (2019-04-07 14:09:59 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 045afc24124d80c6998d9c770844c67912083506:

  arm64: futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value (2019-04-12 15:04:33 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Fix stack unwinding so we ignore user stacks

- Fix ftrace module PLT trampoline initialisation checks

- Fix terminally broken implementation of FUTEX_WAKE_OP atomics

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64/ftrace: fix inadvertent BUG() in trampoline check

Will Deacon (2):
      arm64: backtrace: Don't bother trying to unwind the userspace stack
      arm64: futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value

 arch/arm64/include/asm/futex.h  | 16 ++++++++--------
 arch/arm64/include/asm/module.h |  5 +++++
 arch/arm64/kernel/ftrace.c      |  3 +--
 arch/arm64/kernel/traps.c       | 15 +++++++++------
 4 files changed, 23 insertions(+), 16 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for -rc5
Date: Fri, 12 Apr 2019 17:05:15 +0100	[thread overview]
Message-ID: <20190412160515.GH31037@fuggles.cambridge.arm.com> (raw)

Hi Linus,

Please pull these three arm64 fixes for -rc5. The main thing is a fix to
our FUTEX_WAKE_OP implementation which was unbelievably broken, but did
actually work for the one scenario that GLIBC used to use.

Summary in the tag.

Thanks,

Will

--->8

The following changes since commit 15ade5d2e7775667cf191cf2f94327a4889f8b9d:

  Linux 5.1-rc4 (2019-04-07 14:09:59 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 045afc24124d80c6998d9c770844c67912083506:

  arm64: futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value (2019-04-12 15:04:33 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Fix stack unwinding so we ignore user stacks

- Fix ftrace module PLT trampoline initialisation checks

- Fix terminally broken implementation of FUTEX_WAKE_OP atomics

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64/ftrace: fix inadvertent BUG() in trampoline check

Will Deacon (2):
      arm64: backtrace: Don't bother trying to unwind the userspace stack
      arm64: futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value

 arch/arm64/include/asm/futex.h  | 16 ++++++++--------
 arch/arm64/include/asm/module.h |  5 +++++
 arch/arm64/kernel/ftrace.c      |  3 +--
 arch/arm64/kernel/traps.c       | 15 +++++++++------
 4 files changed, 23 insertions(+), 16 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-04-12 16:05 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 16:05 Will Deacon [this message]
2019-04-12 16:05 ` [GIT PULL] arm64 fixes for -rc5 Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-04-13 17:40   ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-02-16 11:58 Will Deacon
2024-02-16 11:58 ` Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2024-02-16 18:52   ` pr-tracker-bot
2023-10-06  7:56 Will Deacon
2023-10-06  7:56 ` Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-10-06 15:15   ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:44 ` Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 11:45   ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2023-07-21 17:28   ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 11:37 ` Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2022-09-11 19:36   ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 13:53 ` Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-06 18:40   ` Linus Torvalds
2021-08-09 10:52   ` Will Deacon
2021-08-09 10:52     ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-08-06 18:48   ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 14:54 ` Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2021-03-25 19:13   ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 14:39 ` Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-07-10 16:55   ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 15:12 ` Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2020-03-06 20:55   ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 15:02 ` Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-06-14 16:20   ` pr-tracker-bot
2019-02-01 17:51 Will Deacon
2019-02-01 17:51 ` Will Deacon
2019-02-02  1:00 ` pr-tracker-bot
2019-02-02  1:00   ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2018-05-11 17:30 ` Will Deacon
2017-03-31 17:15 Will Deacon
2017-03-31 17:15 ` Will Deacon
2016-06-24 11:41 Will Deacon
2016-06-24 11:41 ` Will Deacon
2016-02-19 16:29 Will Deacon
2016-02-19 16:29 ` Will Deacon
2015-10-07 14:20 Will Deacon
2015-10-07 14:20 ` Will Deacon
2015-01-16 17:16 Will Deacon
2015-01-16 17:16 ` Will Deacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190412160515.GH31037@fuggles.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.