From: Luis Henriques <luis.henriques@canonical.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
gaoyang.zyh@taobao.com, LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ?
Date: Fri, 02 Aug 2013 14:57:03 +0100 [thread overview]
Message-ID: <8761vo2o28.fsf@canonical.com> (raw)
In-Reply-To: <20130802111455.GA29304@gmail.com> (Ingo Molnar's message of "Fri, 2 Aug 2013 13:14:55 +0200")
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
next prev parent reply other threads:[~2013-08-02 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 9:37 stable: a59f4e079d19464eebb9b06513a1d4f55fdae5ba needs backport ? Li Zefan
2013-08-02 11:14 ` Ingo Molnar
2013-08-02 13:57 ` Luis Henriques [this message]
2013-08-08 4:08 ` Li Zefan
2013-08-09 0:00 ` Greg Kroah-Hartman
2013-08-09 1:08 ` Li Zefan
2013-08-31 20:38 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761vo2o28.fsf@canonical.com \
--to=luis.henriques@canonical.com \
--cc=gaoyang.zyh@taobao.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.