All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: ashwin.chaugule@celunite.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	mikukkon@iki.fi, Mika Kukkonen <mikukkon@miku.homelinux.net>,
	linux-mm@kvack.org, ashwin.chaugule@gmail.com
Subject: Re: [PATCH] Bug in mm/thrash.c function grab_swap_token()
Date: Sun, 13 May 2007 16:15:06 -0400	[thread overview]
Message-ID: <464771CA.3080906@redhat.com> (raw)
In-Reply-To: <1178866168.4497.6.camel@localhost.localdomain>

Ashwin Chaugule wrote:
> On Thu, 2007-05-10 at 15:29 -0700, Andrew Morton wrote:
>> On Thu, 10 May 2007 15:24:00 +0300
>> Mika Kukkonen <mikukkon@miku.homelinux.net> wrote:
>>
>>> Following bug was uncovered by compiling with '-W' flag:
>>>
>>>   CC      mm/thrash.o
>>> mm/thrash.c: In function A?AcAcA?A!A?A?grab_swap_tokenA?AcAcA?A!AcA?Ac:
>>> mm/thrash.c:52: warning: comparison of unsigned expression < 0 is always false
>>>
>>> Variable token_priority is unsigned, so decrementing first and then
>>> checking the result does not work; fixed by reversing the test, patch
>>> attached (compile tested only). 
>>>
>>> I am not sure if likely() makes much sense in this new situation, but
>>> I'll let somebody else to make a decision on that.
>>>
>>> Signed-off-by: Mika Kukkonen <mikukkon@iki.fi>
>>>
>>> diff --git a/mm/thrash.c b/mm/thrash.c
>>> index 9ef9071..c4c5205 100644
>>> --- a/mm/thrash.c
>>> +++ b/mm/thrash.c
>>> @@ -48,9 +48,8 @@ void grab_swap_token(void)
>>>  		if (current_interval < current->mm->last_interval)
>>>  			current->mm->token_priority++;
>>>  		else {
>>> -			current->mm->token_priority--;
>>> -			if (unlikely(current->mm->token_priority < 0))
>>> -				current->mm->token_priority = 0;
>>> +			if (likely(current->mm->token_priority > 0))
>>> +				current->mm->token_priority--;
>>>  		}
>>>  		/* Check if we deserve the token */
>>>  		if (current->mm->token_priority >
>> argh.
>>
>> This has potential to cause large changes in system performance.
> 
> I'm not sure how. Although, I think the logic still remains the same.
> IOW, if the prio decrements to zero, it will remain zero until it
> contends for token rapidly. 

The problem is that the original code would decrement an
unsigned variable beyond zero, underflowing to a number
just under 2^32...

That would make the process basically a permanent owner
of the swap token.

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2007-05-13 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070510122359.GA16433@srv1-m700-lanp.koti>
2007-05-10 22:29 ` [PATCH] Bug in mm/thrash.c function grab_swap_token() Andrew Morton
2007-05-11  6:49   ` Ashwin Chaugule
2007-05-11  6:58     ` ashwin chaugule
2007-05-13 20:15     ` Rik van Riel [this message]
2007-05-14  7:38       ` ashwin chaugule

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=464771CA.3080906@redhat.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ashwin.chaugule@celunite.com \
    --cc=ashwin.chaugule@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=mikukkon@iki.fi \
    --cc=mikukkon@miku.homelinux.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.