From: Allen Ashley <ashley@alumni.caltech.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.2.15 kernel bug report
Date: Tue, 3 Apr 2001 01:53:26 -0700 [thread overview]
Message-ID: <200104030853.BAA00238@aa.home.org> (raw)
I am enclosing a section of code that crashes the 2.2.15 kernel
repeatedly. My system is a 266 Intel P2 with 128Mb ram. The
crash is caused by the connect statement. It does not crash
if the socket is in BLOCKING mode. My distribution is Slack 7.0
if that matters.
---------------------------------------------------------------
soval=fcntl(s,F_GETFL,0);
ioval=fcntl(0,F_GETFL,0);
fcntl(s,F_SETFL,soval|O_NONBLOCK);
fcntl(0,F_SETFL,ioval|O_NONBLOCK);
cwait=WAITCONNECT;
*chin=0;
do{
/*If the following line is commented out the program does not crash*/
rval=connect(s, (struct sockaddr *)&dst, sizeof(dst));
read(0,chin,16);
sleep(1);
} while((rval) && --cwait && *chin!=0xa);
fcntl(s,F_SETFL,soval&~O_NONBLOCK);
fcntl(0,F_SETFL,ioval&~O_NONBLOCK);
---------------------------------------------------------------
next reply other threads:[~2001-04-03 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 8:53 Allen Ashley [this message]
2001-04-03 10:21 ` 2.2.15 kernel bug report Tim Waugh
2001-04-03 11:43 ` James Stevenson
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=200104030853.BAA00238@aa.home.org \
--to=ashley@alumni.caltech.edu \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox