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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C27BC433F5 for ; Sat, 12 Mar 2022 00:40:48 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5D3678D0002; Fri, 11 Mar 2022 19:40:47 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 582D38D0001; Fri, 11 Mar 2022 19:40:47 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 472C58D0002; Fri, 11 Mar 2022 19:40:47 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0157.hostedemail.com [216.40.44.157]) by kanga.kvack.org (Postfix) with ESMTP id 37E2C8D0001 for ; Fri, 11 Mar 2022 19:40:47 -0500 (EST) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id E7E679F312 for ; Sat, 12 Mar 2022 00:40:46 +0000 (UTC) X-FDA: 79233878892.20.DD8344E Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf13.hostedemail.com (Postfix) with ESMTP id E338620017 for ; Sat, 12 Mar 2022 00:40:45 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E14FE61324; Sat, 12 Mar 2022 00:40:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2DBAC340E9; Sat, 12 Mar 2022 00:40:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1647045644; bh=rIspAVW+lHYp0djF3IVWFDQH2VFxaJS8HGNJbIZ1Fio=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=vsPXBm2ovwqjqLfwFerKwP6kBpAmPnBMVIV0Qo7ctA18MMiUJ68+VmQlRYvi6zQ9A z247vGDqulqI+mLL6lqu1DdC82uJSKMf6R1jWOZNoRqaXJejbaNsYatr5MCA+nh3f0 BQCFBQSRLFFmB9j7CHIg1qd2/b6JpPJz6fuCrzv8= Date: Fri, 11 Mar 2022 16:40:43 -0800 From: Andrew Morton To: Sebastian Andrzej Siewior Cc: Marcelo Tosatti , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Minchan Kim , Matthew Wilcox , Mel Gorman , Nicolas Saenz Julienne , Juri Lelli , Thomas Gleixner , "Paul E. McKenney" , Ingo Molnar , Peter Zijlstra , Steven Rostedt , Daniel Bristot de Oliveira Subject: Re: [patch v5] mm: lru_cache_disable: replace work queue synchronization with synchronize_rcu Message-Id: <20220311164043.e5e4f3bcac2b472792085f47@linux-foundation.org> In-Reply-To: References: <20220304163554.8872fe5d5a9d634f7a2884f5@linux-foundation.org> <20220310182326.5b375da6b86e95f7e71acd90@linux-foundation.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: E338620017 X-Stat-Signature: 388mxspb5hzwihqc4m9x5s4raseiapsq Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=vsPXBm2o; dmarc=none; spf=pass (imf13.hostedemail.com: domain of akpm@linux-foundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Rspam-User: X-HE-Tag: 1647045645-157148 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, 11 Mar 2022 09:35:49 +0100 Sebastian Andrzej Siewior wrote: > + sched division >=20 > On 2022-03-10 18:23:26 [-0800], Andrew Morton wrote: > > On Thu, 10 Mar 2022 10:22:12 -0300 Marcelo Tosatti wrote: > > > On systems that run FIFO:1 applications that busy loop, > > > any SCHED_OTHER task that attempts to execute > > > on such a CPU (such as work threads) will not > > > be scheduled, which leads to system hangs. > =E2=80=A6 > >=20 > > Permitting a realtime thread to hang the entire system warrants a > > -stable backport, I think. That's just rude. >=20 > I'm not sure if someone is not willingly breaking the system. Based on > my experience, a thread with an elevated priority (that FIFO, RR or DL) > should not hog the CPU. A normal user (!root && !CAP_SYS_NICE) can't > increase the priority of the task. > To avoid a system hangup there is sched_rt_runtime_us which ensures tha= t > all RT threads are throttled once the RT class exceed a certain amount > of runtime. This has been relaxed a little on systems with more CPUs so > that the RT runtime can be shared but this sharing (RT_RUNTIME_SHARE) > has been disabled by default a while ago. That safe switch > (sched_rt_runtime_us) can be disabled and is usually disabled on RT > system since the RT tasks usually run longer especially in corner cases= . Does all this apply if the kernel is non-preemptible? Marcelo, do you know how the offending system bypassed the failsafe?