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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B2F4C61D97 for ; Sun, 29 Jan 2023 05:07:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229833AbjA2FE3 (ORCPT ); Sun, 29 Jan 2023 00:04:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229436AbjA2FE2 (ORCPT ); Sun, 29 Jan 2023 00:04:28 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 490092311A for ; Sat, 28 Jan 2023 21:04:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:Content-Type:MIME-Version: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:In-Reply-To:References; bh=EIeb3tYigQdQQu2QAN1E4TK1fEpNoz1lwF4gQOrE3/M=; b=OVyI2nha5AZ+cpYJ/hDd9Sg1+g X+nseqpOR0yBlcCzkuuwMSVEXkS+A9YrtgYEppXgSdXzHUbixE08QwH//0RZ14CFrV30+tTIIz/GQ s1cDLM/DWIp+pV6uJ3aQzgvPJL1E+rVdbgc0/V1COxu8egGfNy23OkiyWKN9mEhdq8vtSZHBHCYlh AcOF6OTt1vLiaIZ0LQGQI02bKVa/HfynWuAnOjWO8ZwgBMGE1sdWw+SXOWv5f8kShPHpTxEnMnWKY bKa5I6Ll3IcudDne1cREd2zrka8FgJJ7Y6YdWw7sdK4AuAB5K5+fx10PhFhEVpPCaxtd6sU4Qzf9R i5/Bb74w==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1pLzrQ-0013lK-Ke; Sun, 29 Jan 2023 05:04:12 +0000 Date: Sat, 28 Jan 2023 21:04:12 -0800 From: Luis Chamberlain To: lsf-pc@lists.linux-foundation.org, Christoph Hellwig , djwong@kernel.org, song@kernel.org, rafael@kernel.org, gregkh@linuxfoundation.org, viro@zeniv.linux.org.uk, jack@suse.cz Cc: linux-fsdevel@vger.kernel.org Subject: LSF/MM/BPF 2023 BoF: removing kthread freezer next steps Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: Luis Chamberlain Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Probably best as a BoF: Based on feedback from the v3 RFC it would seem we *may* be on the final stretch from s/RFC/PATCH in removing the kthread freezer APIs from filesystems [0]. To be clear that's not to say this is done, but just that it seems we have some agreement towards what to do and this just needs to get baked now, and the last part -- obviously tested. Kthread freezing was added to *help* with the lack of the VFS layer dealing with freezing / thawing for us. But if you look, a few subsystems make use of the kthread freezer API now. So after we complete removal on the filesystems side of things, does anyone see issues with just doing similar removal from other subsystems? Or has the kthread freezer API now been embraced for other reasons other than the original one? [0] https://lkml.kernel.org/r/20230114003409.1168311-1-mcgrof@kernel.org Luis