From: Danilo Krummrich <dakr@kernel.org>
To: Yonatan Maman <Ymaman@nvidia.com>
Cc: nouveau@lists.freedesktop.org, Gal Shalom <GalShalom@nvidia.com>
Subject: Re: [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error
Date: Mon, 30 Sep 2024 13:20:32 +0200 [thread overview]
Message-ID: <ZvqJgMVBs2kAWguk@pollux> (raw)
In-Reply-To: <20240923135449.356244-3-Ymaman@Nvidia.com>
On Mon, Sep 23, 2024 at 01:54:58PM +0000, Yonatan Maman wrote:
> A copy push command might fail, causing `migrate_to_ram` to return a
> dirty HIGH_USER page to the user.
>
> This exposes a security vulnerability in the nouveau driver. To prevent
> memory leaks in `migrate_to_ram` upon a copy error, allocate a zero
> page for the destination page.
So, you refer to the case where this function fails in nouveau_dmem_copy_one()?
If so, can you please explain why adding __GFP_ZERO to alloc_page_vma() helps
with that?
>
> Signed-off-by: Yonatan Maman <Ymaman@Nvidia.com>
> Signed-off-by: Gal Shalom <GalShalom@Nvidia.com>
Since this is a bug, please also add a 'Fixes' tag, CC stable and add a
'Co-developed-by' tag if appropriate.
> ---
> drivers/gpu/drm/nouveau/nouveau_dmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_dmem.c b/drivers/gpu/drm/nouveau/nouveau_dmem.c
> index 6fb65b01d778..097bd3af0719 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_dmem.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_dmem.c
> @@ -193,7 +193,7 @@ static vm_fault_t nouveau_dmem_migrate_to_ram(struct vm_fault *vmf)
> if (!spage || !(src & MIGRATE_PFN_MIGRATE))
> goto done;
>
> - dpage = alloc_page_vma(GFP_HIGHUSER, vmf->vma, vmf->address);
> + dpage = alloc_page_vma(GFP_HIGHUSER | __GFP_ZERO, vmf->vma, vmf->address);
> if (!dpage)
> goto done;
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-09-30 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 13:54 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-23 13:54 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-30 11:09 ` Danilo Krummrich
2024-10-07 12:35 ` Yonatan Maman
2024-09-23 13:54 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-30 11:20 ` Danilo Krummrich [this message]
2024-10-07 12:28 ` Yonatan Maman
2024-10-07 13:51 ` Danilo Krummrich
-- strict thread matches above, loose matches on Subject: below --
2024-09-29 12:30 [PATCH 0/2] *** drm/nouveau/dmem: Fix Memory Leaking and Device Channels configuration*** Yonatan Maman
2024-09-29 12:30 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-29 12:16 [PATCH 0/2] *** drm/nouveau/dmem: Fix Memory Leaking and Device Channels configuration*** Yonatan Maman
2024-09-29 12:16 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-29 12:08 [PATCH 0/2] *** drm/nouveau/dmem: BUG Fixes for Nouveau DMEM*** Yonatan Maman
2024-09-29 12:08 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-29 11:44 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-29 11:44 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-18 15:41 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-18 15:41 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
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=ZvqJgMVBs2kAWguk@pollux \
--to=dakr@kernel.org \
--cc=GalShalom@nvidia.com \
--cc=Ymaman@nvidia.com \
--cc=nouveau@lists.freedesktop.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.