mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: dwmw2@infradead.org, bunk@stusta.de, johnstul@us.ibm.com,
	drepper@redhat.com, Franz.Fischer@goyellow.de,
	linux-kernel@vger.kernel.org
Subject: Re: [UPDATE PATCH][Bug 5132] fix sys_poll() large timeout handling
Date: Fri, 9 Sep 2005 18:16:58 -0700	[thread overview]
Message-ID: <20050909181658.221eb6f9.akpm@osdl.org> (raw)
In-Reply-To: <20050910003525.GC24225@us.ibm.com>

Nishanth Aravamudan <nacc@us.ibm.com> wrote:
>
> Description: The current sys_poll() implementation does not seem to
>  handle large timeouts correctly. Any value in milliseconds (@timeout)
>  which exceeds the maximum representable jiffy value
>  (MAX_SCHEDULE_TIMEOUT) should result in a MAX_SCHEDULE_TIMEOUT
>  schedule_timeout() request. To achieve this, convert @timeout to jiffies
>  first, then compare to MAX_SCHEDULE_TIMEOUT.

The above doesn't describe the bug very well.

>  Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> 
>  ---
> 
>   fs/select.c |   17 ++++++++++-------
>   1 file changed, 10 insertions(+), 7 deletions(-)
> 
>  diff -urpN 2.6.13/fs/select.c 2.6.13-dev/fs/select.c
>  --- 2.6.13/fs/select.c	2005-08-28 17:46:14.000000000 -0700
>  +++ 2.6.13-dev/fs/select.c	2005-09-09 17:22:30.000000000 -0700
>  @@ -469,13 +469,16 @@ asmlinkage long sys_poll(struct pollfd _
>   	if (nfds > current->files->max_fdset && nfds > OPEN_MAX)
>   		return -EINVAL;
>   
>  -	if (timeout) {
>  -		/* Careful about overflow in the intermediate values */
>  -		if ((unsigned long) timeout < MAX_SCHEDULE_TIMEOUT / HZ)

This is the problem to which you're referring, yes?

We're comparing milliseconds with jiffies/HZ, yes?

>  -			timeout = (unsigned long)(timeout*HZ+999)/1000+1;
>  -		else /* Negative or overflow */
>  -			timeout = MAX_SCHEDULE_TIMEOUT;
>  -	}
>  +	if (timeout > 0)
>  +		/*
>  +		 * Convert the value from msecs to jiffies - if overflow
>  +		 * occurs we get a negative value, which gets handled by
>  +		 * the next block
>  +		 */
>  +		timeout = msecs_to_jiffies(timeout) + 1;
>  +	if (timeout < 0) /* Negative requests result in infinite timeouts */
>  +		timeout = MAX_SCHEDULE_TIMEOUT;
>  +	/* 0 case falls through */

I don't particularly like the idea of relying on msecs_to_jiffies(too much)
returning a negative value.

Why can't we do

	int too_much;

	/*
	 * We compare HZ with 1000 to work out which side of the expression
	 * needs conversion.  Because we want to avoid converting any value
	 * to a numerically higher value, which could overflow.
	 */
#if HZ > 1000
	too_much = timeout > jiffies_to_msecs(MAX_SCHEDULE_TIMEOUT);
#else
	too_much = msecs_to_jiffies(timeout) > MAX_SCHEDULE_TIMEOUT;
#endif

	if (too_much)
		timeout = MAX_SCHEDULE_TIMEOUT;

And while we're there, let's stop using the same variable for two different
units - it's horrid.  How about we nuke `timeout' and create timeout_msecs
and timeout_jiffies to show what units they're in?


  reply	other threads:[~2005-09-10  1:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 20:01 [PATCH][Bug " Nishanth Aravamudan
2005-09-06 21:25 ` Nishanth Aravamudan
2005-09-10  0:35   ` [UPDATE PATCH][Bug " Nishanth Aravamudan
2005-09-10  1:16     ` Andrew Morton [this message]
2005-09-10  2:23       ` Nishanth Aravamudan
2005-09-10  2:36         ` Andrew Morton
2005-09-10  2:55           ` Nishanth Aravamudan
2005-09-12 14:30             ` Peter Staubach
2005-09-12 15:05               ` Nishanth Aravamudan
2005-09-12 15:19                 ` Peter Staubach
2005-09-12 16:06                   ` Nishanth Aravamudan

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=20050909181658.221eb6f9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Franz.Fischer@goyellow.de \
    --cc=bunk@stusta.de \
    --cc=drepper@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nacc@us.ibm.com \
    /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

Powered by JetHome