All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2] tcp-lp 2.6.18-rc6: fix tcp_lp_remote_hz_estimator() about rhz
Date: Sun, 3 Dec 2006 13:32:07 +0100	[thread overview]
Message-ID: <20061203123207.GA17178@janus> (raw)
In-Reply-To: <3feffd230609040244o497070f2j7909c6268f4eb588@mail.gmail.com>

On Mon, Sep 04, 2006 at 05:44:58PM +0800, Wong Edison wrote:
> pageexec report an oops for tcp_lp_owd_calculator(). This is due to
> tcp_lp_remote_hz_estimator can return 0.
> 
> This patch fix the handling of lp->flag, so will set lp->flag as FALSE
> if rhz <= 0
> 
> Signed-off-by: Wong Hoi Sing Edison <hswong3i@gmail.com>
> 
> ---
> 
> diff -urpN 2.6.18-rc6/tcp_lp.c tcp-lp/tcp_lp.c
> --- 2.6.18-rc6/tcp_lp.c	2006-09-04 16:21:00.000000000 +0800
> +++ tcp-lp/tcp_lp.c	2006-09-04 17:22:19.000000000 +0800
> @@ -153,14 +157,17 @@ static u32 tcp_lp_remote_hz_estimator(st
> 	if (m < 0)
> 		m = -m;
> 
> -	if (rhz != 0) {
> +	if (rhz > 0) {
> 		m -= rhz >> 6;	/* m is now error in remote HZ est */
> 		rhz += m;	/* 63/64 old + 1/64 new */
> 	} else
> 		rhz = m << 6;
> 
> 	/* record time for successful remote HZ calc */
> -	lp->flag |= LP_VALID_RHZ;
> +	if (rhz > 0)
> +		lp->flag |= LP_VALID_RHZ;
> +	else
> +		lp->flag &= ~LP_VALID_RHZ;
> 
>  out:
> 	/* record reference time stamp */
> 
> -- 
> VGER BF report: U 0.500057

Got bitten by this zerodivide in 2.6.18.* (every few days a panic inside
an interrupt handler) and it doesn't seem to be fixed in 2.6.19.

-- 
Frank

  reply	other threads:[~2006-12-03 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04  9:44 [PATCH 1/2] tcp-lp 2.6.18-rc6: fix tcp_lp_remote_hz_estimator() about rhz Wong Edison
2006-12-03 12:32 ` Frank van Maarseveen [this message]
2006-12-11  6:40   ` David Miller

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=20061203123207.GA17178@janus \
    --to=frankvm@frankvm.com \
    --cc=netdev@vger.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 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.