From: "Denis V. Lunev" <den@sw.ru>
To: Anton Arapov <aarapov@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: kernel panic when only one unsecured port available
Date: Wed, 10 Oct 2007 10:54:52 +0400 [thread overview]
Message-ID: <470C773C.2050700@sw.ru> (raw)
In-Reply-To: <m3bqb89yjw.fsf@bandura.englab.brq.redhat.com>
This code is broken from the very beginning.
iris den # cat /proc/sys/net/ipv4/ip_local_port_range
32768 61000
iris den # echo 32768 32 >/proc/sys/net/ipv4/ip_local_port_range
iris den # cat /proc/sys/net/ipv4/ip_local_port_range
32768 32
iris den # echo 32768 61000 >/proc/sys/net/ipv4/ip_local_port_range
Regards,
Den
Anton Arapov wrote:
> Steps to reproduce:
> Server:
> [root@server ~]# cat /etc/exports
> /export *(ro,insecure)
> // there is insecure ... I am using ports like "1024 to 61000"
> [root@server ~] service nfs restart
>
> Client:
> 1.[root@client ~]# echo 32768 32768 > /proc/sys/net/ipv4/ip_local_port_range
> 32768 32768
> // two same numbers, for ex "32769 32769" etc.
> 2.[root@client ~]# cat /proc/sys/net/ipv4/ip_local_port_range
> 32768 32768
> 3.[root@client ~]# mount server:/export /import
>
> Actual results:
> Kernel always panics
>
> --------------------------------------------------------------------
> [PATCH] ipv4: kernel panic when only one unsecured port available
>
> Patch prevents division by zero. Kernel panics if only one
> unsecured port available.
>
> Signed-off-by: Anton Arapov <aarapov@redhat.com>
> ---
>
> net/ipv4/inet_connection_sock.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
> index fbe7714..00ad079 100644
> --- a/net/ipv4/inet_connection_sock.c
> +++ b/net/ipv4/inet_connection_sock.c
> @@ -80,7 +80,7 @@ int inet_csk_get_port(struct inet_hashinfo *hashinfo,
> int low = sysctl_local_port_range[0];
> int high = sysctl_local_port_range[1];
> int remaining = (high - low) + 1;
> - int rover = net_random() % (high - low) + low;
> + int rover = net_random() % remaining + low;
>
> do {
> head = &hashinfo->bhash[inet_bhashfn(rover, hashinfo->bhash_size)];
>
next prev parent reply other threads:[~2007-10-10 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 14:01 [PATCH] ipv4: kernel panic when only one unsecured port available Anton Arapov
2007-10-10 6:54 ` Denis V. Lunev [this message]
2007-10-10 8:19 ` Anton Arapov
2007-10-10 8:27 ` Denis V. Lunev
2007-10-10 8:31 ` Anton Arapov
2007-10-10 8:38 ` Denis V. Lunev
2007-10-10 8:44 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-10-09 13:59 Anton Arapov
2007-10-15 19:49 ` Andrew Morton
2007-10-15 20:06 ` David Miller
2007-10-15 21:00 ` Andrew Morton
2007-10-16 5:59 ` Anton Arapov
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=470C773C.2050700@sw.ru \
--to=den@sw.ru \
--cc=aarapov@redhat.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.