linux-kernel - Re: [PATCH v2] mm: oom_kill: add trace logs in process

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: <20220816173556.cb493d6a85edd65e1fa52911@linux-foundation.org>
Date:   Tue, 16 Aug 2022 17:35:56 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Pratyush Brahma <pbrahma@....qualcomm.com>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        quic_charante@...cinc.com,
        Pratyush Brahma <quic_pbrahma@...cinc.com>
Subject: Re: [PATCH v2] mm: oom_kill: add trace logs in process_mrelease()
 system call

On Tue, 16 Aug 2022 11:30:17 +0530 Pratyush Brahma <pbrahma@....qualcomm.com> wrote:

> The process_mrelease() system call[1] is used to release the memory of
> a dying process from the context of the caller, which is similar to and
> uses the functions of the oom reaper logic. There exists trace logs for
> a process when reaped by the oom reaper. Just extend the same to when
> done by the process_mrelease() system call.

Why?  Please describe in full detail the end-user value of this change.