From: Sasha Levin <sashal@kernel.org>
To: Phil Auld <pauld@redhat.com>
Cc: tip-bot for Phil Auld <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org, mingo@kernel.org,
efault@gmx.de, Anton Blanchard <anton@ozlabs.org>,
Ben Segall <bsegall@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
stable@vger.kernel.org
Subject: Re: [tip:sched/core] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup
Date: Mon, 8 Apr 2019 10:50:26 -0400 [thread overview]
Message-ID: <20190408145026.GG4689@sasha-vm> (raw)
In-Reply-To: <20190408134214.GC6584@lorien.usersys.redhat.com>
On Mon, Apr 08, 2019 at 09:42:14AM -0400, Phil Auld wrote:
>On Fri, Apr 05, 2019 at 02:15:23PM +0000 Sasha Levin wrote:
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a -stable tag.
>> The stable tag indicates that it's relevant for the following trees: all
>>
>> The bot has tested the following trees: v5.0.6, v4.19.33, v4.14.110, v4.9.167, v4.4.178, v3.18.138.
>>
>> v5.0.6: Failed to apply! Possible dependencies:
>> c0ad4aa4d841 ("sched/fair: Robustify CFS-bandwidth timer locking")
>>
>> v4.19.33: Failed to apply! Possible dependencies:
>> c0ad4aa4d841 ("sched/fair: Robustify CFS-bandwidth timer locking")
>>
>> v4.14.110: Failed to apply! Possible dependencies:
>> c0ad4aa4d841 ("sched/fair: Robustify CFS-bandwidth timer locking")
>>
>
>This is a minor context difference. There is no actual dependency on the
>c0ad4aa4d841 patch. It would be easy to produce new version that could
>go in these trees. I'm not sure what the right action is in that case.
>Should I spin a new version with the different locking in the context?
Please do :)
The algorithm does the dependency analysis by looking at surrounding
code rather than actual functional dependency.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-04-08 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:00 [PATCH v2] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup Phil Auld
2019-03-21 18:01 ` Peter Zijlstra
2019-03-21 18:32 ` Phil Auld
2019-04-03 8:38 ` [tip:sched/core] " tip-bot for Phil Auld
[not found] ` <20190405141524.05DDA2186A@mail.kernel.org>
2019-04-08 13:42 ` Phil Auld
2019-04-08 14:50 ` Sasha Levin [this message]
2019-04-08 17:03 ` Phil Auld
2019-04-08 17:06 ` Sasha Levin
2019-04-08 17:31 ` Phil Auld
2019-04-09 12:48 ` Phil Auld
2019-04-09 13:05 ` Peter Zijlstra
2019-04-09 13:15 ` Phil Auld
2019-04-16 13:33 ` Phil Auld
2019-04-16 16:18 ` Phil Auld
2019-04-16 15:32 ` [tip:sched/urgent] sched/fair: Limit sched_cfs_period_timer() " tip-bot for Phil Auld
2019-04-16 19:26 ` Phil Auld
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=20190408145026.GG4689@sasha-vm \
--to=sashal@kernel.org \
--cc=anton@ozlabs.org \
--cc=bsegall@google.com \
--cc=efault@gmx.de \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.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.