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: <20240611115950.35197b36eafe0a804ecaa0de@linux-foundation.org>
Date: Tue, 11 Jun 2024 11:59:50 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrii Nakryiko <andrii@...nel.org>
Cc: linux-fsdevel@...r.kernel.org, brauner@...nel.org,
 viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
 gregkh@...uxfoundation.org, linux-mm@...ck.org, liam.howlett@...cle.com,
 surenb@...gle.com, rppt@...nel.org, Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH v4 0/7] ioctl()-based API to query VMAs from
 /proc/<pid>/maps


(Please cc Alexey on procfs changes)

On Tue, 11 Jun 2024 04:00:48 -0700 Andrii Nakryiko <andrii@...nel.org> wrote:

> Implement binary ioctl()-based interface to /proc/<pid>/maps file to allow
> applications to query VMA information more efficiently than reading *all* VMAs
> nonselectively through text-based interface of /proc/<pid>/maps file.

Looks nice but I'll await further reviewer input.

> 
> ...
>
>  Documentation/filesystems/proc.rst          |   9 +
>  fs/proc/task_mmu.c                          | 366 +++++++++++--
>  include/uapi/linux/fs.h                     | 156 +++++-
>  tools/include/uapi/linux/fs.h               | 550 ++++++++++++++++++++
>  tools/testing/selftests/bpf/.gitignore      |   1 +
>  tools/testing/selftests/bpf/Makefile        |   2 +-
>  tools/testing/selftests/bpf/procfs_query.c  | 386 ++++++++++++++
>  tools/testing/selftests/bpf/test_progs.c    |   3 +
>  tools/testing/selftests/bpf/test_progs.h    |   2 +
>  tools/testing/selftests/bpf/trace_helpers.c | 104 +++-
>  10 files changed, 1508 insertions(+), 71 deletions(-)
>  create mode 100644 tools/include/uapi/linux/fs.h
>  create mode 100644 tools/testing/selftests/bpf/procfs_query.c

Should the selftests be under bpf/?  This is a procfs feature which
could be used by many things apart from bpf and it really isn't a bpf
thing at all.  Wouldn't tools/testing/selftests/proc/ be a more
appropriate place?


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ