stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?

DISCUSSION Applied Li Zefan 5 participants 7 messages Aug 2, 2013 – Aug 31, 2013 Stable branch

Share & tools

Li Zefan

author

2013-08-02 09:37 UTC #0 lore raw

commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba

Author: Zhu Yanhai <[email protected]>
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. ]

Ingo Molnar

Acked-by

2013-08-02 11:14 UTC #1 lore raw

Quoted 10 lines · Li Zefan

commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai <[email protected]>
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.

Quoted 5 lines

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 <[email protected]>

Thanks,

Ingo

Luis Henriques

2013-08-02 13:57 UTC #2 lore raw

Quoted 24 lines · Ingo Molnar

Quoted 10 lines · Li Zefan
commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai <[email protected]>
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.
Quoted 5 lines
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 <[email protected]>

Quoted 7 lines

Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

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

Cheers,

Signature · 1 line

Luis

Li Zefan

author

2013-08-08 04:08 UTC #3 lore raw

In reply to Ingo Molnar

Hi Greg,

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

Quoted 29 lines · Ingo Molnar

Quoted 10 lines · Li Zefan
commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai <[email protected]>
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.
Quoted 5 lines
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 <[email protected]>
Thanks,
Ingo

Greg Kroah-Hartman

maintainer

2013-08-09 00:00 UTC #4 lore raw

Quoted 3 lines · Li Zefan

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

Li Zefan

author

2013-08-09 01:08 UTC #5 lore raw

Quoted 7 lines · Greg Kroah-Hartman

Quoted 3 lines · Li Zefan
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.

Ben Hutchings

Applied

2013-08-31 20:38 UTC #6 lore raw

In reply to Ingo Molnar

Quoted 15 lines · Ingo Molnar

Quoted 13 lines · Li Zefan
commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai <[email protected]>
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:

Quoted 8 lines

Quoted 2 lines
[ 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 <[email protected]>

I've queued this up for 3.2, thanks.

Ben.

Signature · 3 lines

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