linux-kernel - Re: [PATCH] mm, oom_reaper: make sure that mmput_async is called only when memory was reaped

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Jun 2016 15:44:59 +0200
From:	Michal Hocko <mhocko@...nel.org>
To:	kbuild test robot <lkp@...el.com>
Cc:	kbuild-all@...org, Andrew Morton <akpm@...ux-foundation.org>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	David Rientjes <rientjes@...gle.com>, linux-mm@...ck.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm, oom_reaper: make sure that mmput_async is called
 only when memory was reaped

On Tue 07-06-16 20:30:24, kbuild test robot wrote:
[...]
>    mm/oom_kill.c: In function '__oom_reap_task':
> >> mm/oom_kill.c:490:7: warning: passing argument 1 of 'mmget_not_zero' from incompatible pointer type
>      if (!mmget_not_zero(&mm->mm_users)) {
>           ^

Sigh... My rate of screw ups during rebase for last minute changes is
just too high. Sorry about that!
-- 
Michal Hocko
SUSE Labs