linux-kernel - Re: [GIT PULL] ring-buffer: Updates for v6.15

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: <CAHk-=wjhT_xPdATLmfmdWCM7gKApvTyino_ffko5z1YumJDAHA@mail.gmail.com>
Date: Thu, 27 Mar 2025 19:19:33 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Masami Hiramatsu <mhiramat@...nel.org>, 
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Feng Yang <yangfeng@...inos.cn>, 
	Jiapeng Chong <jiapeng.chong@...ux.alibaba.com>
Subject: Re: [GIT PULL] ring-buffer: Updates for v6.15

On Thu, 27 Mar 2025 at 19:17, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> But NO, that is *not* what is used by the code.
>
> You literally use "struct page *" whenever you want to mmap it.
>
> If the *only* thing that was used was the virtual address, this
> wouldn't be a discussion.

Just to clarify: if you don't mmap this into user space, then that's
fine. Then you can keep just the kernel virtual address.

And I already told you that that is one option: just don't mmap.

But as long as you insist on mmaping the buffer into user space, you
follow the rules. And the rules are that you don't play games. You do
this RIGHT, or you don't do it at all.

And you don't lie about things and claim that the only thing that is
used is the kernel virtual address.

Comprende?

                 Linus