From owner-freebsd-hackers Sun Aug 3 21:23:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA11771 for hackers-outgoing; Sun, 3 Aug 1997 21:23:27 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11762 for ; Sun, 3 Aug 1997 21:23:22 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA26367; Sun, 3 Aug 1997 22:23:17 -0600 (MDT) Date: Sun, 3 Aug 1997 22:23:17 -0600 (MDT) Message-Id: <199708040423.WAA26367@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Charles Henrich Cc: Michael Smith , tom@sdf.com, freebsd-hackers@freebsd.org Subject: Re: tty-level buffer overflows In-Reply-To: <19970803112147.21483@crh.cl.msu.edu> References: <19970803025730.57257@crh.cl.msu.edu> <199708030852.SAA13473@genesis.atrad.adelaide.edu.au> <19970803112147.21483@crh.cl.msu.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Your application is busted; data is arriving faster than your app is reading > > it, and the kernel has run out of patience and started throwing the data > > away. > > Im afraid not, the application is a software Upload, with a singly byte ack > every 2k, if the serial port cant handle that, theres a problem. I would > presume that if the buffer is full, a write() should block. You've got a 16 byte FIFO, and you're wondering why it's overflowing when your application is trying to get 2K at a time? You've *GOT* to be kidding, right? Nate