From: Andrey Konovalov <andreyknvl@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrey Konovalov <andreyknvl@google.com>,
Kees Cook <keescook@chromium.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
Kostya Serebryany <kcc@google.com>,
Evgeniy Stepanov <eugenis@google.com>,
Lee Smith <Lee.Smith@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Jacob Bramley <Jacob.Bramley@arm.com>,
Ruben Ayrapetyan <Ruben.Ayrapetyan@arm.com>,
Chintan Pandya <cpandya@codeaurora.org>
Subject: [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt
Date: Mon, 6 Aug 2018 18:40:44 +0200 [thread overview]
Message-ID: <5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com> (raw)
In-Reply-To: <cover.1533573460.git.andreyknvl@google.com>
Add a note that work on passing tagged user pointers to the kernel via
syscalls has started, but might not be complete yet.
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
---
Documentation/arm64/tagged-pointers.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm64/tagged-pointers.txt b/Documentation/arm64/tagged-pointers.txt
index a25a99e82bb1..361481283f00 100644
--- a/Documentation/arm64/tagged-pointers.txt
+++ b/Documentation/arm64/tagged-pointers.txt
@@ -35,8 +35,9 @@ Using non-zero address tags in any of these locations may result in an
error code being returned, a (fatal) signal being raised, or other modes
of failure.
-For these reasons, passing non-zero address tags to the kernel via
-system calls is forbidden, and using a non-zero address tag for sp is
+Some initial work for supporting non-zero address tags passed to the
+kernel via system calls has been done, but the kernel doesn't provide
+any guarantees at this point. Using a non-zero address tag for sp is
strongly discouraged.
Programs maintaining a frame pointer and frame records that use non-zero
--
2.18.0.597.ga71716f1ad-goog
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Konovalov <andreyknvl@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrey Konovalov <andreyknvl@google.com>,
Kees Cook <keescook@chromium.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
Kostya Serebryany <kcc@google.com>,
Evgeniy Stepanov <eugenis@google.com>,
Lee Smith <Lee.Smith@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Jacob Bramley <Jacob.Bramley@arm.com>,
Ruben Ayrapetyan <Ruben.Ayrapetyan@arm.com>,
Chintan Pandya <cpandya@codeaurora.org>
Subject: [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt
Date: Mon, 6 Aug 2018 18:40:44 +0200 [thread overview]
Message-ID: <5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com> (raw)
In-Reply-To: <cover.1533573460.git.andreyknvl@google.com>
Add a note that work on passing tagged user pointers to the kernel via
syscalls has started, but might not be complete yet.
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
---
Documentation/arm64/tagged-pointers.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm64/tagged-pointers.txt b/Documentation/arm64/tagged-pointers.txt
index a25a99e82bb1..361481283f00 100644
--- a/Documentation/arm64/tagged-pointers.txt
+++ b/Documentation/arm64/tagged-pointers.txt
@@ -35,8 +35,9 @@ Using non-zero address tags in any of these locations may result in an
error code being returned, a (fatal) signal being raised, or other modes
of failure.
-For these reasons, passing non-zero address tags to the kernel via
-system calls is forbidden, and using a non-zero address tag for sp is
+Some initial work for supporting non-zero address tags passed to the
+kernel via system calls has been done, but the kernel doesn't provide
+any guarantees at this point. Using a non-zero address tag for sp is
strongly discouraged.
Programs maintaining a frame pointer and frame records that use non-zero
--
2.18.0.597.ga71716f1ad-goog
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: andreyknvl at google.com (Andrey Konovalov)
Subject: [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt
Date: Mon, 6 Aug 2018 18:40:44 +0200 [thread overview]
Message-ID: <5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com> (raw)
In-Reply-To: <cover.1533573460.git.andreyknvl@google.com>
Add a note that work on passing tagged user pointers to the kernel via
syscalls has started, but might not be complete yet.
Signed-off-by: Andrey Konovalov <andreyknvl at google.com>
---
Documentation/arm64/tagged-pointers.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm64/tagged-pointers.txt b/Documentation/arm64/tagged-pointers.txt
index a25a99e82bb1..361481283f00 100644
--- a/Documentation/arm64/tagged-pointers.txt
+++ b/Documentation/arm64/tagged-pointers.txt
@@ -35,8 +35,9 @@ Using non-zero address tags in any of these locations may result in an
error code being returned, a (fatal) signal being raised, or other modes
of failure.
-For these reasons, passing non-zero address tags to the kernel via
-system calls is forbidden, and using a non-zero address tag for sp is
+Some initial work for supporting non-zero address tags passed to the
+kernel via system calls has been done, but the kernel doesn't provide
+any guarantees at this point. Using a non-zero address tag for sp is
strongly discouraged.
Programs maintaining a frame pointer and frame records that use non-zero
--
2.18.0.597.ga71716f1ad-goog
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: andreyknvl@google.com (Andrey Konovalov)
Subject: [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt
Date: Mon, 6 Aug 2018 18:40:44 +0200 [thread overview]
Message-ID: <5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com> (raw)
Message-ID: <20180806164044.JAFGjXF-XSb2TW0ZhNxHiZDNh_2nmKyKOmNewmm-Xy4@z> (raw)
In-Reply-To: <cover.1533573460.git.andreyknvl@google.com>
Add a note that work on passing tagged user pointers to the kernel via
syscalls has started, but might not be complete yet.
Signed-off-by: Andrey Konovalov <andreyknvl at google.com>
---
Documentation/arm64/tagged-pointers.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm64/tagged-pointers.txt b/Documentation/arm64/tagged-pointers.txt
index a25a99e82bb1..361481283f00 100644
--- a/Documentation/arm64/tagged-pointers.txt
+++ b/Documentation/arm64/tagged-pointers.txt
@@ -35,8 +35,9 @@ Using non-zero address tags in any of these locations may result in an
error code being returned, a (fatal) signal being raised, or other modes
of failure.
-For these reasons, passing non-zero address tags to the kernel via
-system calls is forbidden, and using a non-zero address tag for sp is
+Some initial work for supporting non-zero address tags passed to the
+kernel via system calls has been done, but the kernel doesn't provide
+any guarantees at this point. Using a non-zero address tag for sp is
strongly discouraged.
Programs maintaining a frame pointer and frame records that use non-zero
--
2.18.0.597.ga71716f1ad-goog
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: andreyknvl@google.com (Andrey Konovalov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt
Date: Mon, 6 Aug 2018 18:40:44 +0200 [thread overview]
Message-ID: <5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com> (raw)
In-Reply-To: <cover.1533573460.git.andreyknvl@google.com>
Add a note that work on passing tagged user pointers to the kernel via
syscalls has started, but might not be complete yet.
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
---
Documentation/arm64/tagged-pointers.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm64/tagged-pointers.txt b/Documentation/arm64/tagged-pointers.txt
index a25a99e82bb1..361481283f00 100644
--- a/Documentation/arm64/tagged-pointers.txt
+++ b/Documentation/arm64/tagged-pointers.txt
@@ -35,8 +35,9 @@ Using non-zero address tags in any of these locations may result in an
error code being returned, a (fatal) signal being raised, or other modes
of failure.
-For these reasons, passing non-zero address tags to the kernel via
-system calls is forbidden, and using a non-zero address tag for sp is
+Some initial work for supporting non-zero address tags passed to the
+kernel via system calls has been done, but the kernel doesn't provide
+any guarantees at this point. Using a non-zero address tag for sp is
strongly discouraged.
Programs maintaining a frame pointer and frame records that use non-zero
--
2.18.0.597.ga71716f1ad-goog
next prev parent reply other threads:[~2018-08-06 16:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 16:40 [PATCH v5 00/10] arm64: untag user pointers passed to the kernel Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 01/10] arm64: add type casts to untagged_addr macro Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 02/10] uaccess: add untagged_addr definition for other arches Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 03/10] arm64: untag user addresses in access_ok and __uaccess_mask_ptr Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 04/10] mm, arm64: untag user addresses in mm/gup.c Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 05/10] lib, arm64: untag addrs passed to strncpy_from_user and strnlen_user Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 06/10] arm64: untag user address in __do_user_fault Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 07/10] fs, arm64: untag user address in copy_mount_options Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 08/10] usb, arm64: untag user addresses in devio Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov [this message]
2018-08-06 16:40 ` [PATCH v5 09/10] arm64: update Documentation/arm64/tagged-pointers.txt Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` [PATCH v5 10/10] selftests, arm64: add a selftest for passing tagged pointers to kernel Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` Andrey Konovalov
2018-08-06 16:40 ` andreyknvl
2018-08-06 16:40 ` Andrey Konovalov
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=5396af31a51aaafd5d65742d1cc48854513be778.1533573460.git.andreyknvl@google.com \
--to=andreyknvl@google.com \
--cc=Jacob.Bramley@arm.com \
--cc=Lee.Smith@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Ruben.Ayrapetyan@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cpandya@codeaurora.org \
--cc=dvyukov@google.com \
--cc=eugenis@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kcc@google.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@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 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.