From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
airlied@linux.ie, daniel@ffwll.ch, torvalds@linux-foundation.org,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
keescook@chromium.org, hpa@zytor.com
Cc: linux-arch@vger.kernel.org, linux-mm@kvack.org,
intel-gfx@lists.freedesktop.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] uaccess: Selectively open read or write user access
Date: Fri, 29 May 2020 14:20:25 +1000 (AEST) [thread overview]
Message-ID: <49YBF530k9z9sSs@ozlabs.org> (raw)
In-Reply-To: <2e73bc57125c2c6ab12a587586a4eed3a47105fc.1585898438.git.christophe.leroy@c-s.fr>
On Fri, 2020-04-03 at 07:20:51 UTC, Christophe Leroy wrote:
> When opening user access to only perform reads, only open read access.
> When opening user access to only perform writes, only open write
> access.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> Reviewed-by: Kees Cook <keescook@chromium.org>
Applied to powerpc topic/uaccess, thanks.
https://git.kernel.org/powerpc/c/41cd780524674082b037e7c8461f90c5e42103f0
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
airlied@linux.ie, daniel@ffwll.ch, torvalds@linux-foundation.org,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
keescook@chromium.org, hpa@zytor.com
Cc: linux-arch@vger.kernel.org, linux-mm@kvack.org,
intel-gfx@lists.freedesktop.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 2/5] uaccess: Selectively open read or write user access
Date: Fri, 29 May 2020 14:20:25 +1000 (AEST) [thread overview]
Message-ID: <49YBF530k9z9sSs@ozlabs.org> (raw)
In-Reply-To: <2e73bc57125c2c6ab12a587586a4eed3a47105fc.1585898438.git.christophe.leroy@c-s.fr>
On Fri, 2020-04-03 at 07:20:51 UTC, Christophe Leroy wrote:
> When opening user access to only perform reads, only open read access.
> When opening user access to only perform writes, only open write
> access.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> Reviewed-by: Kees Cook <keescook@chromium.org>
Applied to powerpc topic/uaccess, thanks.
https://git.kernel.org/powerpc/c/41cd780524674082b037e7c8461f90c5e42103f0
cheers
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-29 4:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 7:20 [PATCH v2 1/5] uaccess: Add user_read_access_begin/end and user_write_access_begin/end Christophe Leroy
2020-04-03 7:20 ` [Intel-gfx] " Christophe Leroy
2020-04-03 7:20 ` Christophe Leroy
2020-04-03 7:20 ` [PATCH v2 2/5] uaccess: Selectively open read or write user access Christophe Leroy
2020-04-03 7:20 ` [Intel-gfx] " Christophe Leroy
2020-04-03 7:20 ` Christophe Leroy
2020-05-29 4:20 ` Michael Ellerman [this message]
2020-05-29 4:20 ` [Intel-gfx] " Michael Ellerman
2020-04-03 7:20 ` [PATCH v2 3/5] drm/i915/gem: Replace user_access_begin by user_write_access_begin Christophe Leroy
2020-04-03 7:20 ` [Intel-gfx] " Christophe Leroy
2020-04-03 7:20 ` Christophe Leroy
2020-05-29 4:20 ` Michael Ellerman
2020-05-29 4:20 ` [Intel-gfx] " Michael Ellerman
2020-04-03 7:20 ` [PATCH v2 4/5] powerpc/uaccess: Implement user_read_access_begin and user_write_access_begin Christophe Leroy
2020-04-03 7:20 ` [Intel-gfx] " Christophe Leroy
2020-04-03 7:20 ` Christophe Leroy
2020-05-29 4:24 ` Michael Ellerman
2020-05-29 4:24 ` [Intel-gfx] " Michael Ellerman
2020-04-03 7:20 ` [PATCH v2 5/5] uaccess: Rename user_access_begin/end() to user_full_access_begin/end() Christophe Leroy
2020-04-03 7:20 ` [Intel-gfx] " Christophe Leroy
2020-04-03 7:20 ` Christophe Leroy
2020-04-03 18:01 ` Linus Torvalds
2020-04-03 18:01 ` [Intel-gfx] " Linus Torvalds
2020-04-03 18:01 ` Linus Torvalds
2020-04-03 20:52 ` Al Viro
2020-04-03 20:52 ` [Intel-gfx] " Al Viro
2020-04-03 20:52 ` Al Viro
2020-04-21 2:49 ` Al Viro
2020-04-21 2:49 ` [Intel-gfx] " Al Viro
2020-04-21 2:49 ` Al Viro
2020-04-21 9:12 ` Russell King - ARM Linux admin
2020-04-21 9:12 ` [Intel-gfx] " Russell King - ARM Linux admin
2020-04-21 9:12 ` Russell King - ARM Linux admin
2020-04-21 18:34 ` Linus Torvalds
2020-04-21 18:34 ` [Intel-gfx] " Linus Torvalds
2020-04-21 18:34 ` Linus Torvalds
2020-04-05 18:47 ` Christophe Leroy
2020-04-05 18:47 ` [Intel-gfx] " Christophe Leroy
2020-04-05 18:47 ` Christophe Leroy
2020-04-04 6:20 ` kbuild test robot
2020-04-04 6:20 ` kbuild test robot
2020-04-04 6:20 ` [Intel-gfx] " kbuild test robot
2020-04-04 6:20 ` kbuild test robot
2020-04-04 7:17 ` kbuild test robot
2020-04-04 7:17 ` kbuild test robot
2020-04-04 7:17 ` [Intel-gfx] " kbuild test robot
2020-04-04 7:17 ` kbuild test robot
2020-04-04 7:17 ` kbuild test robot
2020-04-03 16:59 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v2,1/5] uaccess: Add user_read_access_begin/end and user_write_access_begin/end Patchwork
2020-05-29 4:20 ` [PATCH v2 1/5] " Michael Ellerman
2020-05-29 4:20 ` [Intel-gfx] " Michael Ellerman
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=49YBF530k9z9sSs@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=daniel@ffwll.ch \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.