On Fri, Dec 6, 2019 at 6:11 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, Dec 03, 2019 at 03:30:05PM -0800, Xuewei Zhang wrote:
> > Backport patch that cleanly applies for 4.19, 4.14, 4.9, 4.4 stable trees:
>
> Did you send this twice?
Yes, sorry it's by accident.
>
> And the patch is totally corrupted:
>
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index f77fcd37b226..f0abb8fe0ae9 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -4868,20 +4868,28 @@ static enum hrtimer_restart
> > sched_cfs_period_timer(struct hrtimer *timer)
> > if (++count > 3) {
> > u64 new, old = ktime_to_ns(cfs_b->period);
> >
> > - new = (old * 147) / 128; /* ~115% */
> > - new = min(new, max_cfs_quota_period);
> > -
> > - cfs_b->period = ns_to_ktime(new);
> > -
>
> All of your leading whitespace is gone.
>
> You can't use the web client of gmail to send patches inline, sorry.
>
> Can you fix this up and resend all of the backports, none of these
> worked :(
Sorry for the formatting problem Greg.
I just used `git send-email` to sent out the backports. They are at:
v4.19: https://www.spinics.net/lists/stable/msg347573.html
v4.14: https://www.spinics.net/lists/stable/msg347576.html
v4.9: https://www.spinics.net/lists/stable/msg347577.html
v4.4: https://www.spinics.net/lists/stable/msg347578.html
v3.16: https://www.spinics.net/lists/stable/msg347579.html
Hopefully that could work for you. But if they are still broken somehow
(for which I'd be very sorry), you could consider cherry-picking the patch
from my Github repository (forked from yours):
v4.19: https://github.com/xueweiz/linux/commit/1f2c7fd411a4c332629338571911ae63d3804d0e
v4.14: https://github.com/xueweiz/linux/commit/ccec07bf7842d7ab859fdbbfb79781028e0c1f0d
v4.9: https://github.com/xueweiz/linux/commit/548cd3b8d6a1e663d4a5870daee45f236d75322e
v4.4: https://github.com/xueweiz/linux/commit/1d3b43c3c6612901f5384b8ced4e733072175721
v3.16: https://github.com/xueweiz/linux/commit/f31487e819b78515b3173145d13265b746c72815
Each commit is already based on the current HEAD of the respective branches
in your stable kernel repo.
Please let me know if they still don't work.
Best regards,
Xuewei
>
> greg k-h
