From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Fix __range_ok macro
Date: Thu, 20 Mar 2014 17:42:17 +0000 [thread overview]
Message-ID: <20140320174217.GB28238@arm.com> (raw)
In-Reply-To: <1395246577-22120-1-git-send-email-cov@codeaurora.org>
On Wed, Mar 19, 2014 at 04:29:37PM +0000, Christopher Covington wrote:
> Without this, the following scenario is incorrectly determined
> to be invalid.
>
> addr 0x7f_ffffe000 size 8192 addr_limit 0x80_00000000
>
> This behavior was observed while trying to vmsplice the stack
> as part of a CRIU dump of a process on a system started with the
> norandmaps kernel parameter.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
Thanks, applied.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
Alexander Kartashov <alekskartashov@parallels.com>,
Peter Zijlstra <peterz@infradead.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
"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 v2] arm64: Fix __range_ok macro
Date: Thu, 20 Mar 2014 17:42:17 +0000 [thread overview]
Message-ID: <20140320174217.GB28238@arm.com> (raw)
In-Reply-To: <1395246577-22120-1-git-send-email-cov@codeaurora.org>
On Wed, Mar 19, 2014 at 04:29:37PM +0000, Christopher Covington wrote:
> Without this, the following scenario is incorrectly determined
> to be invalid.
>
> addr 0x7f_ffffe000 size 8192 addr_limit 0x80_00000000
>
> This behavior was observed while trying to vmsplice the stack
> as part of a CRIU dump of a process on a system started with the
> norandmaps kernel parameter.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
Thanks, applied.
--
Catalin
next prev parent reply other threads:[~2014-03-20 17:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 22:41 [RFC PATCH] arm64: Fix __addr_ok and __range_ok macros Christopher Covington
2014-03-05 22:41 ` Christopher Covington
2014-03-06 8:20 ` Michael S. Tsirkin
2014-03-06 8:20 ` Michael S. Tsirkin
2014-03-06 16:08 ` Will Deacon
2014-03-06 16:08 ` Will Deacon
2014-03-07 13:22 ` Christopher Covington
2014-03-07 13:22 ` Christopher Covington
2014-03-13 11:20 ` Catalin Marinas
2014-03-13 11:20 ` Catalin Marinas
2014-03-13 13:41 ` Christopher Covington
2014-03-13 13:41 ` Christopher Covington
2014-03-13 15:53 ` Catalin Marinas
2014-03-13 15:53 ` Catalin Marinas
2014-03-19 16:29 ` [PATCH v2] arm64: Fix __range_ok macro Christopher Covington
2014-03-19 16:29 ` Christopher Covington
2014-03-20 17:42 ` Catalin Marinas [this message]
2014-03-20 17:42 ` Catalin Marinas
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=20140320174217.GB28238@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.