linux-kernel - Re: [BUGFIX][PATCH -mm] fix bad call of memcg_oom

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: <20100618031543.GM4306@balbir.in.ibm.com>
Date:	Fri, 18 Jun 2010 08:45:43 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [BUGFIX][PATCH -mm] fix bad call of memcg_oom_recover at cancel
 move.

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> [2010-06-18 11:17:35]:

> On Fri, 18 Jun 2010 10:57:41 +0900
> Daisuke Nishimura <nishimura@....nes.nec.co.jp> wrote:
> 
> > > May I recommend the following change instead
> > > 
> > > 
> > > Don't crash on a null memcg being passed, check if memcg
> > > is NULL and handle the condition gracefully
> > > 
> > > Signed-off-by: Balbir Singh <balbir@...ux.vnet.ibm.com>
> > > ---
> > >  mm/memcontrol.c |    2 +-
> > >  1 files changed, 1 insertions(+), 1 deletions(-)
> > > 
> > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > index c6ece0a..d71c488 100644
> > > --- a/mm/memcontrol.c
> > > +++ b/mm/memcontrol.c
> > > @@ -1370,7 +1370,7 @@ static void memcg_wakeup_oom(struct mem_cgroup *mem)
> > >  
> > >  static void memcg_oom_recover(struct mem_cgroup *mem)
> > >  {
> > > -	if (mem->oom_kill_disable && atomic_read(&mem->oom_lock))
> > > +	if (mem && mem->oom_kill_disable && atomic_read(&mem->oom_lock))
> > >  		memcg_wakeup_oom(mem);
> > >  }
> > >  
> > I agree to this fix.
> > 
> > Acked-by: Daisuke Nishimura <nishimura@....nes.nec.co.jp>
> > 
> 
> I tend to dislike band-aid in callee. but it's not important here.
> 
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
>

The reason is just to make the reading easier

if (cond)
        func(cond)

if (cond2)
        func(cond2)

It is easier to read

        func(cond)
        ...
        func(cond2)

Provided it is valid for us to test the condition inside func()

This way new callers don't have to worry about using func(). This is
very much like how the free calls work today, they can tolerate a NULL
argument and return gracefully.
 

-- 
	Three Cheers,
	Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/