linux-kernel - Re: [PATCH 0/1] Fix zero copy I/O on __get_user

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250507145402.d162d92fa29130d690461a0b@linux-foundation.org>
Date: Wed, 7 May 2025 14:54:02 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pantelis Antoniou <p.antoniou@...tner.samsung.com>
Cc: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>, Artem Krupotkin
 <artem.k@...sung.com>, Charles Briere <c.briere@...sung.com>, Wade
 Farnsworth <wade.farnsworth@...mens.com>
Subject: Re: [PATCH 0/1] Fix zero copy I/O on __get_user_pages allocated
 pages

On Wed, 7 May 2025 10:41:04 -0500 Pantelis Antoniou <p.antoniou@...tner.samsung.com> wrote:

> One example of that is the 9p filesystem which is commonly used in qemu
> based setups for sharing files with the host.
> 
> In our emulation environment we have noticed failing writes when performing
> I/O from a userspace mapped DRM GEM buffer object.
> The platform does not use VRAM, all graphics memory is regular DRAM memory,
> allocated via __get_free_pages
> 
> The same write was successful from a heap allocated bounce buffer.
> 
> The sequence of events is as follows.
>
> ..
>

There's a lot of good stuff in this [0/N], but a single patch "series"
is cumbersome.  Can you please redo this as a standalone patch in which
the changelog is the union of [0/1] and [1/1]?