This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PING][PATCH][BZ #12847] dprintf/vdprintf can cause fork to fail (child process crash)
- From: Rich Felker <dalias at aerifal dot cx>
- To: OndÅej BÃlka <neleai at seznam dot cz>
- Cc: frekel at zes dot com, libc-alpha at sourceware dot org
- Date: Thu, 17 Oct 2013 15:32:33 -0400
- Subject: Re: [PING][PATCH][BZ #12847] dprintf/vdprintf can cause fork to fail (child process crash)
- Authentication-results: sourceware.org; auth=none
- References: <20130921191346 dot GA9202 at domone dot kolej dot mff dot cuni dot cz> <20131011131727 dot GA16574 at domone dot podge> <20131017144008 dot GD31767 at domone dot podge>
On Thu, Oct 17, 2013 at 04:40:08PM +0200, OndÅej BÃlka wrote:
> On Fri, Oct 11, 2013 at 03:17:27PM +0200, OndÅej BÃlka wrote:
> > On Sat, Sep 21, 2013 at 09:13:46PM +0200, OndÅej BÃlka wrote:
> > > Hi,
> > >
> > > This bug has a simple patch from Frank Reker in bugzilla, see
> > > http://sourceware.org/bugzilla/show_bug.cgi?id=12847
> > >
> > > Is it ok to commit or is cause somewhere else?
> > > One possibility would be adding null check to _IO_lock_init.
> > >
> > ping,
> > Rich will you add bug about dprintf signal safety?
Submitted:
https://sourceware.org/bugzilla/show_bug.cgi?id=16060
Rich