public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: ncardwell@google.com, edumazet@google.com, ycheng@google.com,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP" has been added to the 4.9-stable tree
Date: Thu, 24 Aug 2017 18:38:14 -0700	[thread overview]
Message-ID: <20170825013814.GA5599@kroah.com> (raw)
In-Reply-To: <20170824.182645.422781978971774143.davem@davemloft.net>

On Thu, Aug 24, 2017 at 06:26:45PM -0700, David Miller wrote:
> From: Neal Cardwell <ncardwell@google.com>
> Date: Thu, 24 Aug 2017 21:07:56 -0400
> 
> > On Thu, Aug 24, 2017 at 8:45 PM,  <gregkh@linuxfoundation.org> wrote:
> >>  net/ipv4/tcp_input.c |    3 +--
> >>  1 file changed, 1 insertion(+), 2 deletions(-)
> >>
> >> --- a/net/ipv4/tcp_input.c
> >> +++ b/net/ipv4/tcp_input.c
> >> @@ -3036,8 +3036,7 @@ void tcp_rearm_rto(struct sock *sk)
> >>                         /* delta may not be positive if the socket is locked
> >>                          * when the retrans timer fires and is rescheduled.
> >>                          */
> >> -                       if (delta > 0)
> >> -                               rto = delta;
> >> +                       delta = max(delta, 1);
> > 
> > This probably should be:
> > 
> >   rto = max(delta, 1);
> > 
> > I think the 4.12-stable backport looks good, but the 3.18, 4.4, and
> > 4.9 backports have this issue.
> 
> My bad.
> 
> Greg could you please fix this up for me?

Yes, will do.  Neal, good catch.

greg k-h

      reply	other threads:[~2017-08-25  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  0:45 Patch "tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP" has been added to the 4.9-stable tree gregkh
2017-08-25  1:07 ` Neal Cardwell
2017-08-25  1:26   ` David Miller
2017-08-25  1:38     ` Greg KH [this message]

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=20170825013814.GA5599@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ncardwell@google.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=ycheng@google.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