linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc3
Date: Fri, 26 Nov 2021 13:22:46 +0000	[thread overview]
Message-ID: <20211126132245.GA20204@willie-the-truck> (raw)

Hi Linus,

When you get a chance, please can you pull these three arm64 fixes? The
main one is a fix to the way in which we evaluate the macro arguments to
our uaccess routines, which we _think_ might be the root cause behind
some unkillable tasks we've seen in the Android arm64 CI farm (testing is
ongoing). In any case, it's worth fixing.

Other than that, we've toned down an over-zealous VM_BUG_ON() and fixed
ftrace stack unwinding in a bunch of cases.

Please pull.

Thanks,

Will

--->8

The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:

  Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)

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 94902d849e85093aafcdbea2be8e2beff47233e6:

  arm64: uaccess: avoid blocking within critical sections (2021-11-24 09:16:26 +0000)

----------------------------------------------------------------
arm64 fixes for -rc3

- Evaluate uaccess macro arguments outside of the critical section

- Tighten up VM_BUG_ON() in pmd_populate_kernel() to avoid false positive

- Fix ftrace stack unwinding using HAVE_FUNCTION_GRAPH_RET_ADDR_PTR

----------------------------------------------------------------
Mark Rutland (2):
      arm64: ftrace: use HAVE_FUNCTION_GRAPH_RET_ADDR_PTR
      arm64: uaccess: avoid blocking within critical sections

Pingfan Liu (1):
      arm64: mm: Fix VM_BUG_ON(mm != &init_mm) for trans_pgd

 arch/arm64/include/asm/ftrace.h     | 11 +++++++++
 arch/arm64/include/asm/pgalloc.h    |  2 +-
 arch/arm64/include/asm/stacktrace.h |  6 -----
 arch/arm64/include/asm/uaccess.h    | 48 +++++++++++++++++++++++++++++++------
 arch/arm64/kernel/ftrace.c          |  6 ++---
 arch/arm64/kernel/stacktrace.c      | 18 +++++++-------
 6 files changed, 64 insertions(+), 27 deletions(-)

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

             reply	other threads:[~2021-11-26 13:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 13:22 Will Deacon [this message]
2021-11-26 18:35 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22  0:07 ` Linus Torvalds
2020-02-22  0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2019-01-20  0:04 Will Deacon
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 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=20211126132245.GA20204@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).