From: Frantisek Hrbata <fhrbata@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: rientjes@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com, oleg@redhat.com,
minchan.kim@gmail.com, stable@kernel.org, eteo@redhat.com,
pmatouse@redhat.com
Subject: Re: [PATCH v2 RESEND] oom: fix integer overflow of points in oom_badness
Date: Fri, 2 Dec 2011 21:46:13 +0100 [thread overview]
Message-ID: <20111202204613.GA2297@dhcp-26-164.brq.redhat.com> (raw)
In-Reply-To: <20111202190019.GA13283@suse.de>
On Fri, Dec 02, 2011 at 11:00:19AM -0800, Greg KH wrote:
> On Fri, Dec 02, 2011 at 06:45:27PM +0100, Frantisek Hrbata wrote:
> > An integer overflow will happen on 64bit archs if task's sum of rss, swapents
> > and nr_ptes exceeds (2^31)/1000 value. This was introduced by commit
> >
> > f755a04 oom: use pte pages in OOM score
> >
> > where the oom score computation was divided into several steps and it's no
> > longer computed as one expression in unsigned long(rss, swapents, nr_pte are
> > unsigned long), where the result value assigned to points(int) is in
> > range(1..1000). So there could be an int overflow while computing
> >
> > 176 points *= 1000;
> >
> > and points may have negative value. Meaning the oom score for a mem hog task
> > will be one.
> >
> > 196 if (points <= 0)
> > 197 return 1;
> >
> > For example:
> > [ 3366] 0 3366 35390480 24303939 5 0 0 oom01
> > Out of memory: Kill process 3366 (oom01) score 1 or sacrifice child
> >
> > Here the oom1 process consumes more than 24303939(rss)*4096~=92GB physical
> > memory, but it's oom score is one.
> >
> > In this situation the mem hog task is skipped and oom killer kills another and
> > most probably innocent task with oom score greater than one.
> >
> > The points variable should be of type long instead of int to prevent the int
> > overflow.
> >
> > Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
> > Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > Acked-by: Oleg Nesterov <oleg@redhat.com>
> > Acked-by: David Rientjes <rientjes@google.com>
> > Cc: stable@kernel.org [2.6.36+]
>
> For what it's worth, the stable address has changed to
> stable@vger.kernel.org so you might want to fix that up in future
> submissions.
I was not aware of this change.
>
> I still catch patches that are tagged with this marking, but you will
> not end up posting stuff to the list this way :)
Duly noted :)
>
> thanks,
Thanks Greg!
>
> greg k-h
--
Frantisek Hrbata
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-02 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 8:14 [PATCH] oom: fix integer overflow of points in oom_badness Frantisek Hrbata
2011-10-31 15:28 ` Oleg Nesterov
2011-10-31 15:49 ` Frantisek Hrbata
2011-10-31 15:56 ` [PATCH v2] " Frantisek Hrbata
2011-10-31 14:18 ` KOSAKI Motohiro
2011-10-31 17:42 ` Oleg Nesterov
2011-10-31 18:22 ` David Rientjes
2011-12-02 17:45 ` [PATCH v2 RESEND] " Frantisek Hrbata
2011-12-02 19:00 ` Greg KH
2011-12-02 20:46 ` Frantisek Hrbata [this message]
2011-12-08 3:44 ` David Rientjes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111202204613.GA2297@dhcp-26-164.brq.redhat.com \
--to=fhrbata@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eteo@redhat.com \
--cc=gregkh@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=oleg@redhat.com \
--cc=pmatouse@redhat.com \
--cc=rientjes@google.com \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).