From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-190d.mail.infomaniak.ch (smtp-190d.mail.infomaniak.ch [185.125.25.13]) (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 B667D1FBBFF for ; Mon, 13 Jan 2025 16:55:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.125.25.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736787332; cv=none; b=ctINs9v1iz76jW8kh3if3fO6hWxojfLzZiYNBdPtEiGhp0DB7YH1ZzFoq/95b/pL1CWGL5zju/sGs1cLpFvWdwW4NpZsNHF5qrjj3Zh2QKgghqHgxoRLXAQI0ddBrriKCySwcw3xA1FeRGuLyeuDvbeJlI9yYDxtMO4S4F+rtLI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736787332; c=relaxed/simple; bh=GY3lBzf2jQZTyUqw/KtfO5SPHbgH1lCC/gWVyYIm+aQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JmI6M7ma3x32nzgiHl8JI/SMwEee/JeV7mNsp6QR2awbYO1VBksoplQ/rB6kig+bOhuTMuvw4x/90EXYJaawPk1CW3X6omynr08HYgj2BybkWSfr2E90c6ALQPRwACiVcX7vKGfF8vfyCw43P6i9UPbYbjI+lkPt6h5mQ9C5BqA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=digikod.net; spf=pass smtp.mailfrom=digikod.net; dkim=pass (1024-bit key) header.d=digikod.net header.i=@digikod.net header.b=jHsaj4k+; arc=none smtp.client-ip=185.125.25.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=digikod.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=digikod.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=digikod.net header.i=@digikod.net header.b="jHsaj4k+" Received: from smtp-4-0001.mail.infomaniak.ch (unknown [IPv6:2001:1600:7:10:40ca:feff:fe05:1]) by smtp-4-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4YWz0B1Ys8zy2B; Mon, 13 Jan 2025 17:55:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digikod.net; s=20191114; t=1736787322; bh=y0iyHTodjaLkrMlBHireseWKxknvKBh6g5IkCy7KlqE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jHsaj4k+AfA88WWv+T9RZuahZQsdyxPcLzI3yjWE6x/5GiQPYbXrNoP+vHEWl5HMT C9rlYGCViIiyCPK9XlhaXDjD9NveqAsMnXtR3fsVgvZWtxCpiUilTxy3p+8i/gev1X WBhaX2VCOFCLLbJDe0m7TeG2JHLqWvwo1+5xW9B4= Received: from unknown by smtp-4-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 4YWz091wGWzVgn; Mon, 13 Jan 2025 17:55:21 +0100 (CET) Date: Mon, 13 Jan 2025 17:55:20 +0100 From: =?utf-8?Q?Micka=C3=ABl_Sala=C3=BCn?= To: Christian Brauner Cc: Jann Horn , Al Viro , Eric Paris , Paul Moore , =?utf-8?Q?G=C3=BCnther?= Noack , "Serge E . Hallyn" , Ben Scarlato , Casey Schaufler , Charles Zaffery , Daniel Burgener , Francis Laniel , James Morris , Jeff Xu , Jorge Lucangeli Obes , Kees Cook , Konstantin Meskhidze , Matt Bobrowski , Mikhail Ivanov , Phil Sutter , Praveen K Paladugu , Robert Salvet , Shervin Oloumi , Song Liu , Tahera Fahimi , Tyler Hicks , audit@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, Jeff Layton , Josef Bacik Subject: Re: [PATCH v4 27/30] fs: Add iput() cleanup helper Message-ID: <20250113.shaonge7xieT@digikod.net> References: <20250108154338.1129069-1-mic@digikod.net> <20250108154338.1129069-28-mic@digikod.net> <20250113-endlos-lerche-e1958bd9ce32@brauner> Precedence: bulk X-Mailing-List: audit@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: <20250113-endlos-lerche-e1958bd9ce32@brauner> X-Infomaniak-Routing: alpha On Mon, Jan 13, 2025 at 04:00:31PM +0100, Christian Brauner wrote: > On Mon, Jan 13, 2025 at 03:00:20PM +0100, Jann Horn wrote: > > On Wed, Jan 8, 2025 at 4:44 PM Mickaël Salaün wrote: > > > Add a simple scope-based helper to put an inode reference, similar to > > > the fput() helper. > > > > Cleaning up inode references with scope-based cleanup seems dangerous > > to me because, unlike most resources, holding a reference to an inode > > beyond the lifetime of the associated superblock can actually cause > > memory corruption; and scope-based cleanup is designed based on the > > idea that the order and precise location of dropping a reference don't > > matter so much. > > That's in general a good point and I know there's been opposition to > this in the past when we discussed this. So fine by me. Right, I'll use __free(path_put) instead.