stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Li Zefan]

commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai <gaoyang.zyh@taobao.com>
Date:   Tue Jan 8 12:56:52 2013 +0800

    sched: Fix the broken sched_rr_get_interval()

Without this patch, syscall sched_rr_get_interval() can return wrong
value, and the bug was introduced in 2.6.24, so this looks like a
candidate for stable kernel.

The concern for backporting is that this might break some userspace
programs? As the changelog says:

    [ Since this is an ABI and an old bug, we'll test this via a
      slow upstream route, to hopefully discover any app breakage. ]

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Ingo Molnar]

* Li Zefan <lizefan@huawei.com> wrote:

> commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
> Author: Zhu Yanhai <gaoyang.zyh@taobao.com>
> Date:   Tue Jan 8 12:56:52 2013 +0800
> 
>     sched: Fix the broken sched_rr_get_interval()
> 
> Without this patch, syscall sched_rr_get_interval() can return wrong
> value, and the bug was introduced in 2.6.24, so this looks like a
> candidate for stable kernel.
> 
> The concern for backporting is that this might break some userspace
> programs? As the changelog says:
> 
>     [ Since this is an ABI and an old bug, we'll test this via a
>       slow upstream route, to hopefully discover any app breakage. ]

It appears to have caused no trouble.

So I'm fine with backporting it to older -stable kernels:

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Luis Henriques]

Ingo Molnar <mingo@kernel.org> writes:

> * Li Zefan <lizefan@huawei.com> wrote:
>
>> commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
>> Author: Zhu Yanhai <gaoyang.zyh@taobao.com>
>> Date:   Tue Jan 8 12:56:52 2013 +0800
>> 
>>     sched: Fix the broken sched_rr_get_interval()
>> 
>> Without this patch, syscall sched_rr_get_interval() can return wrong
>> value, and the bug was introduced in 2.6.24, so this looks like a
>> candidate for stable kernel.
>> 
>> The concern for backporting is that this might break some userspace
>> programs? As the changelog says:
>> 
>>     [ Since this is an ABI and an old bug, we'll test this via a
>>       slow upstream route, to hopefully discover any app breakage. ]
>
> It appears to have caused no trouble.
>
> So I'm fine with backporting it to older -stable kernels:
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
>
> Thanks,
>
> 	Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Thanks, I'm queuing it for the 3.5 kernel.

Cheers,
-- 
Luis

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Li Zefan]

Hi Greg,

Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.

On 2013/8/2 19:14, Ingo Molnar wrote:
> 
> * Li Zefan <lizefan@huawei.com> wrote:
> 
>> commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
>> Author: Zhu Yanhai <gaoyang.zyh@taobao.com>
>> Date:   Tue Jan 8 12:56:52 2013 +0800
>>
>>     sched: Fix the broken sched_rr_get_interval()
>>
>> Without this patch, syscall sched_rr_get_interval() can return wrong
>> value, and the bug was introduced in 2.6.24, so this looks like a
>> candidate for stable kernel.
>>
>> The concern for backporting is that this might break some userspace
>> programs? As the changelog says:
>>
>>     [ Since this is an ABI and an old bug, we'll test this via a
>>       slow upstream route, to hopefully discover any app breakage. ]
> 
> It appears to have caused no trouble.
> 
> So I'm fine with backporting it to older -stable kernels:
> 
> Acked-by: Ingo Molnar <mingo@kernel.org>
> 
> Thanks,
> 
> 	Ingo
> 

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Greg Kroah-Hartman]

On Thu, Aug 08, 2013 at 12:08:47PM +0800, Li Zefan wrote:
> Hi Greg,
> 
> Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.

I've already done so, please look at the stable-queue.

thanks,

greg k-h

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Li Zefan]

On 2013/8/9 8:00, Greg Kroah-Hartman wrote:
> On Thu, Aug 08, 2013 at 12:08:47PM +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.
> 
> I've already done so, please look at the stable-queue.
> 

Oh, I see it now. I was cced with other patches but not this one, so
I thought it was overlooked.

Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

[Ben Hutchings]

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

On Fri, 2013-08-02 at 13:14 +0200, Ingo Molnar wrote:
> * Li Zefan <lizefan@huawei.com> wrote:
> 
> > commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
> > Author: Zhu Yanhai <gaoyang.zyh@taobao.com>
> > Date:   Tue Jan 8 12:56:52 2013 +0800
> > 
> >     sched: Fix the broken sched_rr_get_interval()
> > 
> > Without this patch, syscall sched_rr_get_interval() can return wrong
> > value, and the bug was introduced in 2.6.24, so this looks like a
> > candidate for stable kernel.
> > 
> > The concern for backporting is that this might break some userspace
> > programs? As the changelog says:
> > 
> >     [ Since this is an ABI and an old bug, we'll test this via a
> >       slow upstream route, to hopefully discover any app breakage. ]
> 
> It appears to have caused no trouble.
> 
> So I'm fine with backporting it to older -stable kernels:
> 
> Acked-by: Ingo Molnar <mingo@kernel.org>

I've queued this up for 3.2, thanks.

Ben.

-- 
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]