[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YIqFcHj3O2t+JJak@kroah.com>
Date: Thu, 29 Apr 2021 12:07:44 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Arkadiusz Kozdra (Arusekk)" <arek_koz@...pl>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@....de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org,
Alexey Dobriyan <adobriyan@...il.com>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v2] proc: Use seq_read_iter for /proc/*/maps
On Thu, Apr 29, 2021 at 12:05:08PM +0200, Arkadiusz Kozdra (Arusekk) wrote:
> Since seq_read_iter looks mature enough to be used for /proc/<pid>/maps,
> re-allow applications to perform zero-copy data forwarding from it.
>
> Some executable-inspecting tools rely on patching entry point
> instructions with minimal machine code that uses sendfile to read
> /proc/self/maps to stdout. The sendfile call allows them to do it
> faster and without excessive allocations.
What programs do that today? You might want to list them here.
>
> This is inspired by the series by Cristoph Hellwig (linked).
>
> Changes since v1:
>
> only change proc_pid_maps_operations
This should go below the --- line, like the documentation states.
thanks,
greg k-h
Powered by blists - more mailing lists