From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>, kernel <kernel@axis.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: uaccess: fix put_user() with TTBR0 PAN
Date: Mon, 22 Nov 2021 11:09:14 +0100 [thread overview]
Message-ID: <20211122100914.GA30695@axis.com> (raw)
In-Reply-To: <20211119130419.GA25912@lakrids.cambridge.arm.com>
On Fri, Nov 19, 2021 at 02:04:50PM +0100, Mark Rutland wrote:
> I think it would be better to use temporaries in __raw_put_user(), along
> with a comment there, so that the requirement is documented and dealt
> with in once place. Example diff at the end of this mail; I'm happy for
> you to pick that for v2, or I can send it out as a patch if your prefer.
Please feel free to send it out as a patch. Thank you.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>, kernel <kernel@axis.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: uaccess: fix put_user() with TTBR0 PAN
Date: Mon, 22 Nov 2021 11:09:14 +0100 [thread overview]
Message-ID: <20211122100914.GA30695@axis.com> (raw)
In-Reply-To: <20211119130419.GA25912@lakrids.cambridge.arm.com>
On Fri, Nov 19, 2021 at 02:04:50PM +0100, Mark Rutland wrote:
> I think it would be better to use temporaries in __raw_put_user(), along
> with a comment there, so that the requirement is documented and dealt
> with in once place. Example diff at the end of this mail; I'm happy for
> you to pick that for v2, or I can send it out as a patch if your prefer.
Please feel free to send it out as a patch. Thank you.
next prev parent reply other threads:[~2021-11-22 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 16:34 [PATCH] arm64: uaccess: fix put_user() with TTBR0 PAN Vincent Whitchurch
2021-11-18 16:34 ` Vincent Whitchurch
2021-11-19 11:33 ` Will Deacon
2021-11-19 11:33 ` Will Deacon
2021-11-19 13:44 ` Mark Rutland
2021-11-19 13:44 ` Mark Rutland
2021-11-19 13:04 ` Mark Rutland
2021-11-19 13:04 ` Mark Rutland
2021-11-22 10:01 ` Mark Rutland
2021-11-22 10:01 ` Mark Rutland
2021-11-22 10:09 ` Vincent Whitchurch [this message]
2021-11-22 10:09 ` Vincent Whitchurch
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=20211122100914.GA30695@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=catalin.marinas@arm.com \
--cc=kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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.