linux-kernel - Re: [PATCH v13 2/2] Add oom victim's memcg to the oom context information

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: <20180711074933.GA20050@dhcp22.suse.cz>
Date:   Wed, 11 Jul 2018 09:53:46 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     禹舟键 <ufo19890607@...il.com>
Cc:     akpm@...ux-foundation.org, rientjes@...gle.com,
        kirill.shutemov@...ux.intel.com, aarcange@...hat.com,
        penguin-kernel@...ove.sakura.ne.jp, guro@...com,
        yang.s@...baba-inc.com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, Wind Yu <yuzhoujian@...ichuxing.com>
Subject: Re: [PATCH v13 2/2] Add oom victim's memcg to the oom context
 information

On Wed 11-07-18 11:39:29, 禹舟键 wrote:
> Hi Michal
> Sorry , I l forget to update the changlog for the second patch, but
> the cpuset information is not missing.

The cpuset information is missing in the changelog.

> Do I still need to make the
> v14  or just update the changelog for v13?

Wait for more feedback for few days. If there are no other concerns just
repost this patch 2. Btw. I still think that it would be more logical
to print cpuset before memcg info. But I will not insist.
-- 
Michal Hocko
SUSE Labs