linux-kernel - Re: [patch 1/3] mm, oom: organize oom context into struct

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: <alpine.DEB.2.10.1507011429460.14014@chino.kir.corp.google.com>
Date:	Wed, 1 Jul 2015 14:29:57 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Michal Hocko <mhocko@...e.cz>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [patch 1/3] mm, oom: organize oom context into struct

On Wed, 1 Jul 2015, Sergey Senozhatsky wrote:

> On (06/30/15 15:46), David Rientjes wrote:
> > > > There are essential elements to an oom context that are passed around to
> > > > multiple functions.
> > > > 
> > > > Organize these elements into a new struct, struct oom_context, that
> > > > specifies the context for an oom condition.
> > > > 
> > > 
> > > s/oom_context/oom_control/ ?
> > > 
> > 
> > I think it would be confused with the existing memory.oom_control for 
> > memcg.
> > 
> 
> Hello David,
> 
> Sorry, I meant that in commit message you say
> 
> :Organize these elements into a new struct, struct oom_context, that
> :specifies the context for an oom condition.
> 
> but define and use `struct oom_control' (not `struct oom_context')
> 

Oh, point very well taken, thank you.
--
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/