public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Will Lentz <will_lentz@trimble.com>
To: ecos-discuss@ecos.sourceware.org
Cc: Will Lentz <Will_Lentz@Trimble.com>
Subject: [ECOS] uipc_socket.c
Date: Wed, 15 Jun 2005 22:39:00 -0000	[thread overview]
Message-ID: <1118875026.9020.21.camel@localhost.localdomain> (raw)

Hi,

I may have found a potential bug in
packages/net/bsd_tcpip/current/src/sys/kern/uipc_socket.c (or I may be
completely wrong :-).

At the end of sodealloc(), the following code exists:
       zfreei(so->so_zone, so);
       wakeup(so->so_zone);
The problem is that zfreei() changes so->so_zone.  Shouldn't wakeup() be
done on the original so->so_zone?  I only noticed this problem by:
1- while(1) { 
   sock = socket( AF_INET, SOCK_STREAM, IPPROTO_TCP );
   connect( sock, ... );
   close( sock );
   }
   Eventually this pauses in socket() (in cyg_tsleep()) when you run out
of eCos sockets.  

2- After 2*MSL or so, cyg_wakeup() gets called with chan == 0x0.  Why?
The zfreei() call in sodealloc() changes so->so_zone to 0 before the
wakeup() call.

The following diff solves the problem for me by making the wakeup() work
on the so_zone that was freed:

--- uipc_socket.c       Thu Jul 24 11:04:25 2003
+++ new_uipc_socket.c   Wed Jun 15 14:54:20 2005
@@ -202,8 +202,12 @@
                FREE(so->so_accf, M_ACCF);
        }
 #endif /* INET */
-       zfreei(so->so_zone, so);
-        wakeup(so->so_zone);
+       {
+               struct vm_zone *tmp = so->so_zone;
+
+               zfreei(so->so_zone, so);
+               wakeup(tmp);
+       }
 }

Any ideas?  Suggestions?

Thanks,
Will


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2005-06-15 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 22:39 Will Lentz [this message]
2005-06-16  7:06 ` [ECOS] uipc_socket.c (and cyg_tcp_maxidle) Hans Hübner
2005-06-16 15:36   ` Will Lentz
2005-06-16 15:51     ` Hans Hübner
2005-06-16 16:06       ` Will Lentz
     [not found]         ` <20050616183534.N69813@web.m68k.de>
2005-06-16 23:45           ` Will Lentz
2005-06-17  7:15             ` Andrew Lunn
2005-06-17 20:12   ` Andrew Lunn
2005-06-17 21:00     ` Will Lentz

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=1118875026.9020.21.camel@localhost.localdomain \
    --to=will_lentz@trimble.com \
    --cc=ecos-discuss@ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).