From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1C7271AC44D; Mon, 25 May 2026 05:37:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779687428; cv=none; b=c99XjiBtF9kXo7DlyEOxewEH2A0csj6o3LIy9xZkcvbfA3LmU6WuwU1/zkw2DB30OCtFr0hiB1psPlCNmnlLeciYM7Fvd2rw1/Q/2trMIRVJ3TFj11ZIKXw71tUpXTTkU/Ds/qVISIlqB6oG7CN2Ujvx43P2I9o+8PGOOb/mSaA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779687428; c=relaxed/simple; bh=aSUk+GkfuNtV5doxYAl/uvzB5aZCrVlMtp/gV8VEcc0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=I90zeiJYWgAOFwp4TXYvu0ym4Warra1cJ5RW6TBumt2cewEGTkcNhkF8CVo1cAIvZ9WxE09Q/MbZfddhNAQttxeV/8UsJhoznUWOqyhDt+F6LC30sJCKXxawWiyW0sk6zC7g7711iR81/FkKA/VCTST78khY4rHXgNbyVz6pjRY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=mI7+58UN; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="mI7+58UN" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Transfer-Encoding :Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description; bh=bPlnrUAngQhntq0icVQxK0A5R6EP/y6CGfxUmuJ8Roc=; b=mI7+58UNZvQ1rHO+UR+G3zOxD7 /8Q4dyZKxJcdSNb/R47cH8reyDTtiHoTo+ZY1PEHKP1sCy7wV2KEhwd8MNm/M9D7VXNwHZoztfouo ellPDj7sZaVnwIcwtuRKY+kRVN9tGtX3CfEZ+71st7D3jw6OwcdGneEEFEF9XNvEvTxVz0XU8F5v6 aKLKYaDQcv0dpz+Vxwj0TvKoeLyqOXxQt3Fs7io8F6fnGJKSnqnfrBDTuM9Bjn1mwkQsNTWDDnfhD qxzwqs5H2TVfEJQkzZA/O6FF3yMLeD+t3A5pcA1FIZEHbDav7HM47fbADf9+YeeWA6EZTFKtS8mej OhB0Hp4w==; Received: from hch by bombadil.infradead.org with local (Exim 4.99.1 #2 (Red Hat Linux)) id 1wRNzu-0000000GKn6-0I3f; Mon, 25 May 2026 05:37:06 +0000 Date: Sun, 24 May 2026 22:37:06 -0700 From: Christoph Hellwig To: Jaegeuk Kim Cc: Theodore Tso , Christoph Hellwig , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, Matthew Wilcox , linux-f2fs-devel@lists.sourceforge.net, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Akilesh Kailash , Christian Brauner Subject: Re: [f2fs-dev] [PATCH v2] f2fs: another way to set large folio by remembering inode number Message-ID: References: <20260409134538.3692605-1-jaegeuk@kernel.org> <20260521155748.GA79343@macsyma-wired.lan> Precedence: bulk X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Fri, May 22, 2026 at 03:32:39AM +0000, Jaegeuk Kim wrote: > I went this route because Android heavily restricts ioctl() permissions > and we needed broader access for this to work within the framework. It’s > definitely a pragmatic choice just to get it running in production. That is not a good reason. > If ioctl() is a right way for upstream, I'm happy to change this patch. By > the way, I really don't understand why all the messages are so offensive, > even without trying to understand the problem or guiding right directions. The right way is to: 1) Talk to the relevant subsystems (MM and fsdevel), and if it affects userspace that linux-api list and actually explain your use case. 2) And then actually listen to feedback. f2fs just keeps piling these ABI hacks on without any review, and it is causing real problems.