From: Will Deacon <will@kernel.org>
To: ebiederm@xmission.com, suzuki.poulose@arm.com,
mark.rutland@arm.com, elver@google.com, seanjc@google.com,
broonie@kernel.org, David Engraf <david.engraf@sysgo.com>,
catalin.marinas@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: signal: nofpsimd: Do not allocate fp/simd context when not available
Date: Mon, 7 Mar 2022 22:03:29 +0000 [thread overview]
Message-ID: <164668908127.3275060.4752923202018767533.b4-ty@kernel.org> (raw)
In-Reply-To: <20220225104008.820289-1-david.engraf@sysgo.com>
On Fri, 25 Feb 2022 11:40:08 +0100, David Engraf wrote:
> Commit 6d502b6ba1b2 ("arm64: signal: nofpsimd: Handle fp/simd context for
> signal frames") introduced saving the fp/simd context for signal handling
> only when support is available. But setup_sigframe_layout() always
> reserves memory for fp/simd context. The additional memory is not touched
> because preserve_fpsimd_context() is not called and thus the magic is
> invalid.
>
> [...]
Applied to arm64 (for-next/fpsimd), thanks!
[1/1] arm64: signal: nofpsimd: Do not allocate fp/simd context when not available
https://git.kernel.org/arm64/c/0a32c88ddb9a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-03-07 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:40 David Engraf
2022-02-25 17:57 ` Mark Brown
2022-02-28 7:56 ` David Engraf
2022-02-28 13:20 ` Mark Brown
2022-02-28 18:34 ` Catalin Marinas
2022-03-07 22:03 ` Will Deacon [this message]
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=164668908127.3275060.4752923202018767533.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david.engraf@sysgo.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.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=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
/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
all inboxes | Powered by JetHome®