linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc6
Date: Wed, 15 Dec 2021 11:19:18 +0000	[thread overview]
Message-ID: <20211215111917.GB16765@willie-the-truck> (raw)

Hi Linus,

Please pull this pair of arm64 fixes for -rc6. There's a fix for missing
locking around kernel page-table allocation causing a crash with
virtio-mem and a fix for a smatch warning in the kexec code where we
would return 0 on the error path.

With any luck, that's us done for the year.

Cheers,

Will

--->8

The following changes since commit 35b6b28e69985eafb20b3b2c7bd6eca452b56b53:

  arm64: ftrace: add missing BTIs (2021-12-02 10:18:32 +0000)

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 4bfe24b6beb3f2d9426f8ee7b1946dc967a9d0a9:

  arm64: kexec: Fix missing error code 'ret' warning in load_other_segments() (2021-12-13 16:27:57 +0000)

----------------------------------------------------------------
arm64 fixes for -rc6

- Fix fixmap race when creating kernel page-tables

- Fix missing error code on kexec failure path

----------------------------------------------------------------
Jianyong Wu (1):
      arm64/mm: Avoid fixmap race condition when creating pud mappings

Lakshmi Ramasubramanian (1):
      arm64: kexec: Fix missing error code 'ret' warning in load_other_segments()

 arch/arm64/kernel/machine_kexec_file.c | 1 +
 arch/arm64/mm/mmu.c                    | 7 +++++++
 2 files changed, 8 insertions(+)

             reply	other threads:[~2021-12-15 11:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 11:19 Will Deacon [this message]
2021-12-15 16:00 ` [GIT PULL] arm64 fixes for -rc6 Catalin Marinas
2021-12-15 18:49   ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2025-07-09 15:08 Will Deacon
2025-07-09 18:37 ` pr-tracker-bot
2024-11-01 11:22 Will Deacon
2024-11-01 18:34 ` pr-tracker-bot
2024-06-28  8:59 Will Deacon
2024-06-28 17:01 ` pr-tracker-bot
2024-02-23 10:25 Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-09  0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-12  9:14   ` Will Deacon
2017-04-12 10:18     ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 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=20211215111917.GB16765@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=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).