From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C72D9C282CE for ; Mon, 8 Apr 2019 17:06:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 979D621473 for ; Mon, 8 Apr 2019 17:06:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554743176; bh=7cnZNBJiqZwVUWVIbvGO5XsNIgLBaKGw3BF7FLwqRjQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=kdkwC4VtfM2QoiVU1Zs8pSBIv2bVNo9RY+WjW6n4dxeVW6b+PNkDBqVprAYn3nYbS 0DUYoonDgXkI5puQ33TMpUCsJMa4WvAlPt9lV+hU3attFGbiSZIH606rNF7ObVED25 YzF9OrCBo112GTQO2JB4htuXnEekL8/zLtuALtrk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729159AbfDHRGP (ORCPT ); Mon, 8 Apr 2019 13:06:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:46652 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727023AbfDHRGO (ORCPT ); Mon, 8 Apr 2019 13:06:14 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 68B6220880; Mon, 8 Apr 2019 17:06:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554743173; bh=7cnZNBJiqZwVUWVIbvGO5XsNIgLBaKGw3BF7FLwqRjQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=o/uiZOABLOnhNuS8JhpNN9R3+KFenccCUdEmsMlfADBBsvwjNp4npyM5w0H4Qavnf CtuSj8U9yqfXnvYIya3Ole6wm1hHuNSoqNSuuZPIGLo+EJvyPv5SgoOFP20hQr6Kow +OT/i9XeHUU8zv5y33Ilfv0EGaPqWj8HOvma5gps= Date: Mon, 8 Apr 2019 13:06:12 -0400 From: Sasha Levin To: Phil Auld Cc: tip-bot for Phil Auld , linux-tip-commits@vger.kernel.org, mingo@kernel.org, efault@gmx.de, Anton Blanchard , Ben Segall , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , stable@vger.kernel.org Subject: Re: [tip:sched/core] sched/fair: Limit sched_cfs_period_timer loop to avoid hard lockup Message-ID: <20190408170612.GI4689@sasha-vm> References: <20190405141524.05DDA2186A@mail.kernel.org> <20190408134214.GC6584@lorien.usersys.redhat.com> <20190408145026.GG4689@sasha-vm> <20190408170305.GI6584@lorien.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190408170305.GI6584@lorien.usersys.redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Apr 08, 2019 at 01:03:05PM -0400, Phil Auld wrote: >On Mon, Apr 08, 2019 at 10:50:26AM -0400 Sasha Levin wrote: >> 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 :) >> > >Sure. I'm just not sure how to post it. It only shows up in this tip-bot >email and on gitweb. It's not in tip.git and not in Linus' upstream tree. > >I've updated the patch at it will apply now to v5.0.6, v4.19.33, v4.14.110, >v4.9.167, v4.4.178 all with increasing offsets but nothing else. You can either reply to this thread with the patch(es), or just send them out and annotate one way or the other that they should go to their appropriate stable trees. >v3.18.138 won't take it without more work. I'd be inclined to skip that one. No problem there. -- Thanks, Sasha