From: Eduard Roccatello <lilo@roccatello.it>
To: Willy Tarreau <willy@w.ods.org>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ipv4/tcp.c little cleanup
Date: Fri, 23 Jan 2004 21:03:05 +0100 [thread overview]
Message-ID: <200401232103.05618.lilo@roccatello.it> (raw)
In-Reply-To: <20040122234833.GL545@alpha.home.local>
On Friday 23 January 2004 00:48, Willy Tarreau wrote:
> Hi !
>
> On Thu, Jan 22, 2004 at 10:53:37PM +0100, Eduard Roccatello wrote:
> > Hello,
> > i've done a little cleanup to net/ipv4/tcp.c
> >
> > I hope it is ok :-)
>
> I haven't looked at sysctl_max_syn_backlog type, but if it's unsigned,
> there's a risk of infinite loop for values above 2^31 on 32 bits
> machines, or 2^63 on 64 bits machine.
sysctl_max_syn_backlog is an int and max_qlen_log is a u8 (uint8_t).
i think there is no problem with them.
sysctl_max_syn_backlog max value is 1024 so max_qlen_log is just 9.
is it ok for you?
> > --- net/ipv4/tcp.c.orig 2004-01-22 22:49:38.000000000 +0100
> > +++ net/ipv4/tcp.c 2004-01-22 22:42:38.000000000 +0100
> > @@ -549,9 +549,9 @@ int tcp_listen_start(struct sock *sk)
> > return -ENOMEM;
> >
> > memset(lopt, 0, sizeof(struct tcp_listen_opt));
> > - for (lopt->max_qlen_log = 6; ; lopt->max_qlen_log++)
> > - if ((1 << lopt->max_qlen_log) >= sysctl_max_syn_backlog)
> > - break;
> > + lopt->max_qlen_log = 6;
> > + while (sysctl_max_syn_backlog > (1 << lopt->max_qlen_log))
> > + lopt->max_qlen_log++;
> > get_random_bytes(&lopt->hash_rnd, 4);
> >
> > write_lock_bh(&tp->syn_wait_lock);
next prev parent reply other threads:[~2004-01-23 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 21:53 [PATCH] net/ipv4/tcp.c little cleanup Eduard Roccatello
2004-01-22 23:48 ` Willy Tarreau
2004-01-23 20:03 ` Eduard Roccatello [this message]
2004-01-23 22:27 ` Willy Tarreau
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=200401232103.05618.lilo@roccatello.it \
--to=lilo@roccatello.it \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=willy@w.ods.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.