public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jfardo at laurelnetworks dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2074] _IO_new_file_xsputn() in fileops.c not checking for EOF Date: Tue, 25 Apr 2006 21:40:00 -0000 [thread overview] Message-ID: <20060425214023.11079.qmail@sourceware.org> (raw) In-Reply-To: <20051220202817.2074.jfardo@laurelnetworks.com> ------- Additional Comments From jfardo at laurelnetworks dot com 2006-04-25 21:40 ------- I don't have a specific test case any more. This would intermittently cause problems when running 'rpm' to install a package on a file system that was full. If the package being installed was just the right size, rpm would seg fault. The following change in fileops.c fixes the bug. glibc/libio/fileops.c: *************** *** 1371,1376 **** --- 1371,1379 ---- if (do_write) { count = new_do_write (f, s, do_write); + if (count == EOF) { + count = 0; + } to_do -= count; if (count < do_write) return n - to_do; -- 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.
next prev parent reply other threads:[~2006-04-25 21:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-20 20:28 [Bug libc/2074] New: " jfardo at laurelnetworks dot com 2006-04-25 18:42 ` [Bug libc/2074] " drepper at redhat dot com 2006-04-25 21:40 ` jfardo at laurelnetworks dot com [this message] 2006-08-03 18:25 ` drepper at redhat dot com 2006-08-03 18:54 ` jfardo at laurelnetworks dot com 2006-08-28 15:24 ` drepper at redhat dot com 2006-08-29 15:03 ` John dot Fardo at ecitele dot com 2006-08-29 15:34 ` jakub at redhat dot com 2006-08-29 17:43 ` John dot Fardo at ecitele dot com 2006-09-09 17:33 ` drepper at redhat dot com 2010-05-10 23:46 ` [Bug manual/2074] " pasky at suse dot cz 2010-05-11 0:51 ` pasky at suse dot cz
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=20060425214023.11079.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).