From: Frantisek Hrbata <fhrbata@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: rientjes@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
stable@kernel.org, eteo@redhat.com, pmatouse@redhat.com
Subject: Re: [PATCH] oom: fix integer overflow of points in oom_badness
Date: Mon, 31 Oct 2011 16:49:42 +0100 [thread overview]
Message-ID: <20111031154942.GB2280@dhcp-26-164.brq.redhat.com> (raw)
In-Reply-To: <20111031152833.GA31904@redhat.com>
On Mon, Oct 31, 2011 at 04:28:33PM +0100, Oleg Nesterov wrote:
> On 10/31, Frantisek Hrbata wrote:
> >
> > My understanding is that we may just change the type of points variable from int
> > to long and keep the current imho clearer(better readable) computation. There
> > should not be an overflow on 32bit and there is a plenty of space for 64bit.
> > If you like this solution better I will post the patch as v2.
>
> Up to maintainer, but personally I think the simple s/int/long/ looks better.
> Everything like get_mm_*/nr_ptes returns long.
Agreed. I will post v2 with the int => long change.
>
> Anyway good catch. Imho stable needs the fix too.
>
> Cosmetic nit,
>
> > - points = get_mm_rss(p->mm) + p->mm->nr_ptes;
> > - points += get_mm_counter(p->mm, MM_SWAPENTS);
> > + points = (int)((get_mm_rss(p->mm) + get_mm_counter(p->mm, MM_SWAPENTS) +
> ^^^^^
>
> Why do we need the explicit typecast? It buys nothing and looks a bit confusing.
You are right, it's not needed. I just wanted to make the cast more visible, but
some kind of comment would be probably better here.
>
> And, if you prefer "int", perhaps something like
>
> - points *= 1000;
> - points /= totalpages;
> + /* avoid the possible overflow */
> + points = points * 1000L / totalpages;
>
> looks a bit more readable with the same effect. But I won't insist, this is
> up to you and David.
Sure, this looks much better than the one line expression in the patch I sent.
If David or others decide to not go with the int=>long change I think we should
use this.
>
> Oleg.
>
Many thanks Oleg.
--
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-10-31 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 8:14 Frantisek Hrbata
2011-10-31 15:28 ` Oleg Nesterov
2011-10-31 15:49 ` Frantisek Hrbata [this message]
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
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=20111031154942.GB2280@dhcp-26-164.brq.redhat.com \
--to=fhrbata@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eteo@redhat.com \
--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