linux-kernel - Re: [PATCH 2/3] mm/ksm: Support prctl controlling KSM with pid

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] [day] [month] [year] [list]

Message-ID: <fb4235f1-7ad7-443b-a802-7161f9613d21@redhat.com>
Date: Tue, 3 Sep 2024 10:00:14 +0200
From: David Hildenbrand <david@...hat.com>
To: xu xin <xu.xin.sc@...il.com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
 shr@...kernel.io, hughd@...gle.com
Subject: Re: [PATCH 2/3] mm/ksm: Support prctl controlling KSM with pid

On 03.09.24 06:13, xu xin wrote:
> Thanks for your reply.
> 
> Selection of interface
> ======================
> 
> At this point, I have been thinking for a long time, and in order to achieve
> the control of the KSM scanning of an already running process, the current
> prctl PR_SET_MEMORY_MERGE is the most suitable interface. On the one hand,
> it is compatible with the existing KSM PRCTL interface, making it easier
> for users to get used to and adapt to it; On the other hand, it adds prctl
> control over processes that have already been started through PID. Lastly,
> I referred to the PR_SCHED_CORE option of prctl, which also uses arg3 to
> perform operations on tasks pointed to by specific PID.
> 
> Anyway, the current way may not necessarily violates "prctl() manipulates
> various aspects of the behavior of the calling thread or process." ,
> becasue we can consider controlling KSM scanning of pid as a behavior of
> the calling thread.

No, it's just wrong. Find something else.

-- 
Cheers,

David / dhildenb