You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Eric Covener <co...@gmail.com> on 2017/06/06 01:12:23 UTC
Re: The drive for 2.4.26
On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
<st...@greenbytes.de> wrote:
> I have one report of a CPU busy loop that seems to only happen on the last 3 changes in mod_http2. Steffen is currently testing if a feature disable solves the problem and thus points to the cause. I hope to hear from him tomorrow sometime during the day if that addresses the issue or not.
>
> Otherwise I am hesitant to make any more changes from my side and hope we can go forward with a release.
Anything on this?
--
Eric Covener
covener@gmail.com
Re: The drive for 2.4.26
Posted by Jim Jagielski <ji...@jaguNET.com>.
There was a delay in doing the T&R due to an issue that
was being investigated. This looks resolved now. With that,
I plan on doing a T& today at ~1:30pm (Eastern) unless someone
else wishes to RM.
Re: The drive for 2.4.26
Posted by Jim Jagielski <ji...@jaguNET.com>.
Still looking at a T&R today... I will RM unless someone else
would like to do so!
Re: The drive for 2.4.26
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Jun 8, 2017 at 11:07 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> Perfect... I propose a T&R on Monday... comments?
+1. Many will have noticed already, but apr 1.6.2 and apr-util-1.6.0 vote
threads were just spawned to be tallied 13:00 UTC Monday.
Re: The drive for 2.4.26
Posted by Jim Jagielski <ji...@jaguNET.com>.
Perfect... I propose a T&R on Monday... comments?
> On Jun 6, 2017, at 5:23 AM, Stefan Eissing <st...@greenbytes.de> wrote:
>
> Backported. Will also release v1.10.6 on github shortly.
>
>> Am 06.06.2017 um 10:53 schrieb Stefan Eissing <st...@greenbytes.de>:
>>
>>>
>>> Am 06.06.2017 um 10:45 schrieb Plüm, Rüdiger, Vodafone Group <ru...@vodafone.com>:
>>>
>>>
>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Stefan Eissing [mailto:stefan.eissing@greenbytes.de]
>>>> Gesendet: Dienstag, 6. Juni 2017 10:40
>>>> An: dev@httpd.apache.org
>>>> Betreff: Re: The drive for 2.4.26
>>>>
>>>> Proposed the patch as fix, since we did not see the behaviour pop up
>>>> again over the last days at Steffen's system.
>>>>
>>>> I assume the RTC is in place now.
>>>
>>> My personal opinion: Only after 2.4.26 is released. So from my personal point of view you can go ahead backporting.
>>> Others may see this differently.
>>
>> I shall use the time our US friends are still slumbering on to back port the change, taking your statement as an excuse. :-P
>>
>> -Stefan
>>
>>>
>>> Regards
>>>
>>> Rüdiger
>>>
>>>>
>>>> -Stefan
>>>>
>>>>> Am 06.06.2017 um 09:26 schrieb Stefan Eissing
>>>> <st...@greenbytes.de>:
>>>>>
>>>>> I made a patch on Friday evening for Steffen's system where the
>>>> behaviour happens. Hope to hear back from him today.
>>>>>
>>>>> -Stefan
>>>>>
>>>>>> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
>>>>>>
>>>>>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
>>>>>> <st...@greenbytes.de> wrote:
>>>>>>> I have one report of a CPU busy loop that seems to only happen on
>>>> the last 3 changes in mod_http2. Steffen is currently testing if a
>>>> feature disable solves the problem and thus points to the cause. I hope
>>>> to hear from him tomorrow sometime during the day if that addresses the
>>>> issue or not.
>>>>>>>
>>>>>>> Otherwise I am hesitant to make any more changes from my side and
>>>> hope we can go forward with a release.
>>>>>>
>>>>>>
>>>>>> Anything on this?
>>>>>>
>>>>>> --
>>>>>> Eric Covener
>>>>>> covener@gmail.com
>
Re: The drive for 2.4.26
Posted by Stefan Eissing <st...@greenbytes.de>.
Backported. Will also release v1.10.6 on github shortly.
> Am 06.06.2017 um 10:53 schrieb Stefan Eissing <st...@greenbytes.de>:
>
>>
>> Am 06.06.2017 um 10:45 schrieb Plüm, Rüdiger, Vodafone Group <ru...@vodafone.com>:
>>
>>
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Stefan Eissing [mailto:stefan.eissing@greenbytes.de]
>>> Gesendet: Dienstag, 6. Juni 2017 10:40
>>> An: dev@httpd.apache.org
>>> Betreff: Re: The drive for 2.4.26
>>>
>>> Proposed the patch as fix, since we did not see the behaviour pop up
>>> again over the last days at Steffen's system.
>>>
>>> I assume the RTC is in place now.
>>
>> My personal opinion: Only after 2.4.26 is released. So from my personal point of view you can go ahead backporting.
>> Others may see this differently.
>
> I shall use the time our US friends are still slumbering on to back port the change, taking your statement as an excuse. :-P
>
> -Stefan
>
>>
>> Regards
>>
>> Rüdiger
>>
>>>
>>> -Stefan
>>>
>>>> Am 06.06.2017 um 09:26 schrieb Stefan Eissing
>>> <st...@greenbytes.de>:
>>>>
>>>> I made a patch on Friday evening for Steffen's system where the
>>> behaviour happens. Hope to hear back from him today.
>>>>
>>>> -Stefan
>>>>
>>>>> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
>>>>>
>>>>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
>>>>> <st...@greenbytes.de> wrote:
>>>>>> I have one report of a CPU busy loop that seems to only happen on
>>> the last 3 changes in mod_http2. Steffen is currently testing if a
>>> feature disable solves the problem and thus points to the cause. I hope
>>> to hear from him tomorrow sometime during the day if that addresses the
>>> issue or not.
>>>>>>
>>>>>> Otherwise I am hesitant to make any more changes from my side and
>>> hope we can go forward with a release.
>>>>>
>>>>>
>>>>> Anything on this?
>>>>>
>>>>> --
>>>>> Eric Covener
>>>>> covener@gmail.com
Re: The drive for 2.4.26
Posted by Stefan Eissing <st...@greenbytes.de>.
> Am 06.06.2017 um 10:45 schrieb Plüm, Rüdiger, Vodafone Group <ru...@vodafone.com>:
>
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Stefan Eissing [mailto:stefan.eissing@greenbytes.de]
>> Gesendet: Dienstag, 6. Juni 2017 10:40
>> An: dev@httpd.apache.org
>> Betreff: Re: The drive for 2.4.26
>>
>> Proposed the patch as fix, since we did not see the behaviour pop up
>> again over the last days at Steffen's system.
>>
>> I assume the RTC is in place now.
>
> My personal opinion: Only after 2.4.26 is released. So from my personal point of view you can go ahead backporting.
> Others may see this differently.
I shall use the time our US friends are still slumbering on to back port the change, taking your statement as an excuse. :-P
-Stefan
>
> Regards
>
> Rüdiger
>
>>
>> -Stefan
>>
>>> Am 06.06.2017 um 09:26 schrieb Stefan Eissing
>> <st...@greenbytes.de>:
>>>
>>> I made a patch on Friday evening for Steffen's system where the
>> behaviour happens. Hope to hear back from him today.
>>>
>>> -Stefan
>>>
>>>> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
>>>>
>>>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
>>>> <st...@greenbytes.de> wrote:
>>>>> I have one report of a CPU busy loop that seems to only happen on
>> the last 3 changes in mod_http2. Steffen is currently testing if a
>> feature disable solves the problem and thus points to the cause. I hope
>> to hear from him tomorrow sometime during the day if that addresses the
>> issue or not.
>>>>>
>>>>> Otherwise I am hesitant to make any more changes from my side and
>> hope we can go forward with a release.
>>>>
>>>>
>>>> Anything on this?
>>>>
>>>> --
>>>> Eric Covener
>>>> covener@gmail.com
>>>
>
AW: The drive for 2.4.26
Posted by Plüm,
Rüdiger,
Vodafone Group <ru...@vodafone.com>.
> -----Ursprüngliche Nachricht-----
> Von: Stefan Eissing [mailto:stefan.eissing@greenbytes.de]
> Gesendet: Dienstag, 6. Juni 2017 10:40
> An: dev@httpd.apache.org
> Betreff: Re: The drive for 2.4.26
>
> Proposed the patch as fix, since we did not see the behaviour pop up
> again over the last days at Steffen's system.
>
> I assume the RTC is in place now.
My personal opinion: Only after 2.4.26 is released. So from my personal point of view you can go ahead backporting.
Others may see this differently.
Regards
Rüdiger
>
> -Stefan
>
> > Am 06.06.2017 um 09:26 schrieb Stefan Eissing
> <st...@greenbytes.de>:
> >
> > I made a patch on Friday evening for Steffen's system where the
> behaviour happens. Hope to hear back from him today.
> >
> > -Stefan
> >
> >> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
> >>
> >> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
> >> <st...@greenbytes.de> wrote:
> >>> I have one report of a CPU busy loop that seems to only happen on
> the last 3 changes in mod_http2. Steffen is currently testing if a
> feature disable solves the problem and thus points to the cause. I hope
> to hear from him tomorrow sometime during the day if that addresses the
> issue or not.
> >>>
> >>> Otherwise I am hesitant to make any more changes from my side and
> hope we can go forward with a release.
> >>
> >>
> >> Anything on this?
> >>
> >> --
> >> Eric Covener
> >> covener@gmail.com
> >
Re: The drive for 2.4.26
Posted by Stefan Eissing <st...@greenbytes.de>.
Proposed the patch as fix, since we did not see the behaviour pop up again over the last days at Steffen's system.
I assume the RTC is in place now.
-Stefan
> Am 06.06.2017 um 09:26 schrieb Stefan Eissing <st...@greenbytes.de>:
>
> I made a patch on Friday evening for Steffen's system where the behaviour happens. Hope to hear back from him today.
>
> -Stefan
>
>> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
>>
>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
>> <st...@greenbytes.de> wrote:
>>> I have one report of a CPU busy loop that seems to only happen on the last 3 changes in mod_http2. Steffen is currently testing if a feature disable solves the problem and thus points to the cause. I hope to hear from him tomorrow sometime during the day if that addresses the issue or not.
>>>
>>> Otherwise I am hesitant to make any more changes from my side and hope we can go forward with a release.
>>
>>
>> Anything on this?
>>
>> --
>> Eric Covener
>> covener@gmail.com
>
Re: The drive for 2.4.26
Posted by Stefan Eissing <st...@greenbytes.de>.
I made a patch on Friday evening for Steffen's system where the behaviour happens. Hope to hear back from him today.
-Stefan
> Am 06.06.2017 um 03:12 schrieb Eric Covener <co...@gmail.com>:
>
> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> I have one report of a CPU busy loop that seems to only happen on the last 3 changes in mod_http2. Steffen is currently testing if a feature disable solves the problem and thus points to the cause. I hope to hear from him tomorrow sometime during the day if that addresses the issue or not.
>>
>> Otherwise I am hesitant to make any more changes from my side and hope we can go forward with a release.
>
>
> Anything on this?
>
> --
> Eric Covener
> covener@gmail.com