This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PING^2][PATCH][BZ #12847] dprintf/vdprintf can cause fork to fail (child process crash)


On Tue, Nov 05, 2013 at 01:56:08PM -0500, Rich Felker wrote:
> OndÅej,
> 
> Did you miss this message's sibling in the thread, Message-ID:
> <20131017193233.GE20515@brightrain.aerifal.cx>, sent on 17 Oct?
> I submitted it as glibc issue 16060.
>
I pinged if we can procceed with patch.


> Rich
> 
> On Tue, Nov 05, 2013 at 04:12:53PM +0100, OndÅej BÃlka wrote:
> > ping
> > 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?
> > 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]