lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Jun 2009 12:39:56 -0400 From: Theodore Tso <tytso@....edu> To: Thierry Vignaud <tvignaud@...driva.com> Cc: Eric Sandeen <sandeen@...hat.com>, ext4 development <linux-ext4@...r.kernel.org> Subject: Re: [PATCH] debugfs: don't try to fclose NULL On Tue, Jun 30, 2009 at 05:44:55PM +0200, Thierry Vignaud wrote: > Eric Sandeen <sandeen@...hat.com> writes: > > > do_logdump may jump to errout if fopen(out_file) fails, > > but in that case out_file is NULL, and fclose will segfault. > > You should report that segfault to glibc authors too. It would be robust for glibc to code fclose() defensively such that it would survive a null pointer, but I don't think it's technically required by the ANSI or POSIX spec. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists