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]

Date:   Thu, 18 Aug 2022 10:15:59 +0530
From:   Pratyush Brahma <quic_pbrahma@...cinc.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
CC:     <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
        <quic_charante@...cinc.com>, <quic_pkondeti@...cinc.com>
Subject: Re: [PATCH v2] mm: oom_kill: add trace logs in process_mrelease()
 system call


On 17-08-2022 21:32, Andrew Morton wrote:
> On Tue, 16 Aug 2022 11:30:17 +0530 Pratyush Brahma <pbrahma@....qualcomm.com> wrote:
>
>> From: Charan Teja Kalla <quic_charante@...cinc.com>
>>
>> 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.
>>
>> ...
>>
>> +	pr_debug("process_mrelease: reaped process %d (%s), now anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n",
>> +						task_pid_nr(task), task->comm,
>> +						K(get_mm_counter(mm, MM_ANONPAGES)),
>> +						K(get_mm_counter(mm, MM_FILEPAGES)),
>> +						K(get_mm_counter(mm, MM_SHMEMPAGES)));
> This addition wasn't changelogged.  It's the only pr_debug in
> oom_kill.c.  Please explain?

The equivalent pr_info() message as in oom_reap_task_mm() is made 
pr_debug() here as per review comments in patch-set v1.

>