Date: Thu, 31 Jan 2008 10:44:29 -0800 From: Julian Elischer <julian@elischer.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: Daniel Eischen <deischen@freebsd.org>, Gary Stanley <gary@velocity-servers.net>, Landon Fuller <landonf@threerings.net>, freebsd-threads@freebsd.org Subject: Re: threads/119920: fork broken in libpthread Message-ID: <47A2170D.6020308@elischer.org> In-Reply-To: <20080131093321.K35034@fledge.watson.org> References: <200801240850.m0O8o2JQ023500@freefall.freebsd.org> <4798564B.7070500@elischer.org> <Pine.GSO.4.64.0801240957550.16059@sea.ntplx.net> <20080128185830.B56811@fledge.watson.org> <479E3079.3000803@elischer.org> <20080129222455.T53151@fledge.watson.org> <20080131093321.K35034@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > > On Tue, 29 Jan 2008, Robert Watson wrote: > >>>> Should the patch be considered for an errata notice for 6.x? Should >>>> we be trying to MFC this to 7.x for inclusion with 7.0 or does it >>>> need more time to shake out and should potentially be a 7.0 errata >>>> notice or just appear in 7.1? >>> >>> yes and yes and no >> >> If the fix is going to ship in 7.0 and hasn't yet been MFC'd, that >> needs to happen ASAP. Could someone forward the patch/etc over to re@ >> for approval? >> >> The procedure for doing an errata patch is basically that whoever is >> proposing the errata patch needs to e-mail a patch, or multiple >> patches if it's different for different branches, a proposed branch >> list, and as much of a completed errata notice template as possible >> (impact, etc) to re@ for review. Once re@ is OK that it's ready to go, >> it will get sent over to secteam@ to be put into production, binary >> updates generated, etc. If in doubt about which branches, drop e-mail >> to secteam@ to ask which are supported, etc. >> >> At this point we would probably not advise doing the errata patch >> before 7.0 is released, so priority should go to preparing any patches >> that need to go out with 7.0. > > Hello? > > Right now this is on re@'s list of "waiting for this to do RC2", which > means that the release is holding on the fix. Please let me know what > the plan is so we can either move on with the release without waiting, > or have some sort of timeline in mind. Is this patch believed mature > enough to be merged as-is? the releng 6 and releng 7 versions of this patch are at: http://www.freebsd.org/~julian/kse-6.diff and http://www.freebsd.org/~julian/kse-7.diff but the one for 7 is just speculative. I don't have a 7.x system to test. Landon, what is your test case? > > Thanks, > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47A2170D.6020308>