From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20481 invoked by alias); 29 Aug 2006 15:03:53 -0000 Received: (qmail 20368 invoked by alias); 29 Aug 2006 15:03:43 -0000 Date: Tue, 29 Aug 2006 15:03:00 -0000 Message-ID: <20060829150343.20367.qmail@sourceware.org> From: "John dot Fardo at ecitele dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20051220202817.2074.jfardo@laurelnetworks.com> References: <20051220202817.2074.jfardo@laurelnetworks.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/2074] _IO_new_file_xsputn() in fileops.c not checking for EOF X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00209.txt.bz2 List-Id: ------- Additional Comments From John dot Fardo at ecitele dot com 2006-08-29 15:03 ------- Subject: RE: _IO_new_file_xsputn() in fileops.c not checking for EOF It's not very clear from the glibc code, but, isn't _IO_SYSWRITE a wrapper for the system call to write? Are you implying that the write system call should never fail? What do you think will happen when the file system is full? - John Fardo > -----Original Message----- > From: drepper at redhat dot com > [mailto:sourceware-bugzilla@sourceware.org] > Sent: Monday, August 28, 2006 11:25 AM > To: John Fardo > Subject: [Bug libc/2074] _IO_new_file_xsputn() in fileops.c > not checking for EOF > > > ------- Additional Comments From drepper at redhat dot com > 2006-08-28 15:24 ------- Which function called though > _IO_SYSWRITE returns -1? None should, that's the whole point. > > -- > > > http://sourceware.org/bugzilla/show_bug.cgi?id=2074 > > ------- You are receiving this mail because: ------- You > reported the bug, or are watching the reporter. > > -- http://sourceware.org/bugzilla/show_bug.cgi?id=2074 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.