From: Zack Rusin <zackr@vmware.com>
To: "nick.alcock@oracle.com" <nick.alcock@oracle.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"code@siddh.me" <code@siddh.me>,
"pstanner@redhat.com" <pstanner@redhat.com>,
"ddiss@suse.de" <ddiss@suse.de>,
"andy@kernel.org" <andy@kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] Introduce new wrappers to copy user-arrays
Date: Tue, 12 Sep 2023 01:53:47 +0000 [thread overview]
Message-ID: <0f3075867d473d57e769b9a064bccf7b967e162c.camel@vmware.com> (raw)
In-Reply-To: <cover.1694202430.git.pstanner@redhat.com>
On Fri, 2023-09-08 at 21:59 +0200, Philipp Stanner wrote:
> Hi!
>
> David Airlie suggested that we could implement new wrappers around
> (v)memdup_user() for duplicating user arrays.
>
> This small patch series first implements the two new wrapper functions
> memdup_array_user() and vmemdup_array_user(). They calculate the
> array-sizes safely, i.e., they return an error in case of an overflow.
>
> It then implements the new wrappers in two components in kernel/ and two
> in the drm-subsystem.
>
> In total, there are 18 files in the kernel that use (v)memdup_user() to
> duplicate arrays. My plan is to provide patches for the other 14
> successively once this series has been merged.
>
>
> Changes since v1:
> - Insert new headers alphabetically ordered
> - Remove empty lines in functions' docstrings
> - Return -EOVERFLOW instead of -EINVAL from wrapper functions
>
>
> @Andy:
> I test-build it for UM on my x86_64. Builds successfully.
> A kernel build (localmodconfig) for my Fedora38 @ x86_64 does also boot
> fine.
>
> If there is more I can do to verify the early boot stages are fine,
> please let me know!
>
> P.
>
> Philipp Stanner (5):
> string.h: add array-wrappers for (v)memdup_user()
> kernel: kexec: copy user-array safely
> kernel: watch_queue: copy user-array safely
> drm_lease.c: copy user-array safely
> drm: vmgfx_surface.c: copy user-array safely
>
> drivers/gpu/drm/drm_lease.c | 4 +--
> drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 4 +--
> include/linux/string.h | 40 +++++++++++++++++++++++++
> kernel/kexec.c | 2 +-
> kernel/watch_queue.c | 2 +-
> 5 files changed, 46 insertions(+), 6 deletions(-)
>
Series, and in particular the vmwgfx changes, look good to me.
Reviewed-by: Zack Rusin <zackr@vmware.com>
prev parent reply other threads:[~2023-09-12 3:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 19:59 [PATCH v2 0/5] Introduce new wrappers to copy user-arrays Philipp Stanner
2023-09-08 19:59 ` [PATCH v2 1/5] string.h: add array-wrappers for (v)memdup_user() Philipp Stanner
2023-09-10 7:43 ` Andy Shevchenko
2023-09-16 14:32 ` Dan Carpenter
2023-09-18 6:55 ` Andy Shevchenko
2023-09-18 9:13 ` Philipp Stanner
2023-09-08 19:59 ` [PATCH v2 2/5] kernel: kexec: copy user-array safely Philipp Stanner
2023-09-11 0:25 ` Baoquan He
2023-09-08 19:59 ` [PATCH v2 3/5] kernel: watch_queue: " Philipp Stanner
2023-09-08 19:59 ` [PATCH v2 4/5] drm_lease.c: " Philipp Stanner
2023-09-08 19:59 ` [PATCH v2 5/5] drm: vmgfx_surface.c: " Philipp Stanner
2023-09-12 1:27 ` [PATCH v2 0/5] Introduce new wrappers to copy user-arrays Kees Cook
2023-09-12 1:55 ` Dave Airlie
2023-09-12 2:32 ` Kees Cook
2023-09-12 1:53 ` Zack Rusin [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=0f3075867d473d57e769b9a064bccf7b967e162c.camel@vmware.com \
--to=zackr@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=airlied@gmail.com \
--cc=andy@kernel.org \
--cc=brauner@kernel.org \
--cc=code@siddh.me \
--cc=daniel@ffwll.ch \
--cc=ddiss@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=mripard@kernel.org \
--cc=nick.alcock@oracle.com \
--cc=pstanner@redhat.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).