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 BC4B5C07545 for ; Tue, 24 Oct 2023 16:14:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 4AC9C6B02C8; Tue, 24 Oct 2023 12:14:26 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 45E206B02C9; Tue, 24 Oct 2023 12:14:26 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 34B5F6B02CA; Tue, 24 Oct 2023 12:14:26 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 221A16B02C8 for ; Tue, 24 Oct 2023 12:14:26 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id EFA74120459 for ; Tue, 24 Oct 2023 16:14:25 +0000 (UTC) X-FDA: 81380852490.11.B5BFE47 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf03.hostedemail.com (Postfix) with ESMTP id 03BC52002A for ; Tue, 24 Oct 2023 16:14:23 +0000 (UTC) Authentication-Results: imf03.hostedemail.com; dkim=none; spf=pass (imf03.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1698164064; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=31PiJwGjtxPAuf+yofsI1pzM9FudvkexhyMPy7IEVPk=; b=Grm4t3YlfmSICYity6cttpaFEfNujuCotfVIf3fO55FMRUCD8gc8G0MVxHoDJ5Ljq2oxJl Ja+68lhUlzOgWqC0H/Nf1Y2jwqep/Jc7lQSiimwmrXMFjsZQ19d/jv/hqh6Yl9m9GcPYc2 XxVkefJL4gNF5woqy0KGSybtGBMWN68= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1698164064; a=rsa-sha256; cv=none; b=8QdBqCoJKu8hPfNYbj9rO/iLwUFHde8IumXkMc4x8SxNllYRuZBJS18B/ATHt9+ExDd5Ns fwUjJBRaDCgZFQeN5KbKLX6E2C8JC0FYigN3eIzzn90O2KC70fxrqcSKTliEs6ptzMIYr8 fSA/br1Z5TinWVF3L2PvQLID0a5+PPU= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=none; spf=pass (imf03.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none Received: by verein.lst.de (Postfix, from userid 2407) id D7FD668AA6; Tue, 24 Oct 2023 18:14:18 +0200 (CEST) Date: Tue, 24 Oct 2023 18:14:18 +0200 From: Christoph Hellwig To: "Darrick J. Wong" Cc: Christoph Hellwig , Jens Axboe , Matthew Wilcox , Ilya Dryomov , Andrew Morton , linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 1/3] filemap: add a per-mapping stable writes flag Message-ID: <20231024161418.GA20546@lst.de> References: <20231024064416.897956-1-hch@lst.de> <20231024064416.897956-2-hch@lst.de> <20231024150053.GY3195650@frogsfrogsfrogs> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231024150053.GY3195650@frogsfrogsfrogs> User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspamd-Queue-Id: 03BC52002A X-Rspam-User: X-Stat-Signature: xwpj6bjc11gx56xjdx7siyehxf98ftb4 X-Rspamd-Server: rspam03 X-HE-Tag: 1698164063-353357 X-HE-Meta: U2FsdGVkX1+x27tznu4Lsl6h5S2Ciusi6MjCWqA1ZA2u8VvYB/bIwSYD39saFJBB4gtMPGTukn1RC39clDiHn7ICa6bAffMIDU/pCOKxKRI7AQo7Qn73+TZcHBCg1m15zB0oL/EDw4TLFJDGc9/6yfrjjZDFtu2yvPHRLv33SOzjBv5Z8elZBgVCZnwwV1zt20GqmaGu+a2y1HtHBaFa7pyrUTvPQeq7LQtdAn5dA4xIkFg2p6IBlHHwv9BGqO9q0BPGj2tk/8HNBvLKBbSq2yenPrBCJK6MTZ1T8azPVJMafqzOl8ON1hubCuZ68P40tKxX3K2YLcSChgpI50piQiero1suffeYd+Qvl0dTpmL2bbhxEJAX03LXxvc6jrlqG6D7xc/eV24Ym2G1KkXDKvVrtHyrwI8LLn3nq3im7XdM+3fTTtG4OHEbMYSHQHyIXC69Ms91wRkKyd5dCqR+VVw7epdL3XylNKdKq6TenDsw6+AXfyhhJWgIyveJ2poyDre1kW5aLuEKxD2j6Dh0ZIStvjcniBGKcrC4jdkH+texHTS7Y/vWH55wb48Cc6CLpQnQNbSJ07wGWEU4CWMPvsvaOVuSvCIkBSL9ztJ2k2UKjdjp8Hz308qeOsap/cvyShuQspWVbsDCfjnQHOcQDWfen95tfE6ylV2HgkMmZsroTSLyxbWJmy5QXmUZwLDKf4gNAOqD317ViWlObKxbmu+0+s6Jjjs1XNNBf2vefvLAGvo/t5PcN8hWx+aDVM8HppLuXGRSC9TIHuzCpuvnpOE4M4y00n/8Y/msf+5YCPxqfXSHJnQNGSVpQAPEC1ap6ygdwn526EPW58cIIwBFfUsvBIbO/BUcEJin4tWnqXK2IKvlTDkxitKt8KoYN5XzCb8h7r0DMXhk83yeDVxskK1DlFcGBFNwW6UBDNefzuvTT0dMnDTxuBLmzojMUL35NYhqdjkmv/tZFA+VVod MtD6imra C93Xug9tNrbZpvGbyobEHYzndQ+9xmAqPsakmEOfubj9NXBc= 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: List-Subscribe: List-Unsubscribe: On Tue, Oct 24, 2023 at 08:00:53AM -0700, Darrick J. Wong wrote: > For a hot second I wondered if we could get rid of SB_I_STABLE_WRITES > too, but then had an AHA moment when I saw that NFS also sets it. It's not just NFS, but still the general way of propagating the flag. I don't really want to add bdev-specific code to new_inode.