Received: by 2002:a05:7412:3290:b0:fa:6e18:a558 with SMTP id ev16csp897737rdb; Fri, 26 Jan 2024 14:36:42 -0800 (PST) X-Google-Smtp-Source: AGHT+IHQemKe9ObgCd//o+EITB7esVVNvjQuekH6ZWDkmOmAGUsW4N5/5sRjoOmWpZyyj7NOfZZg X-Received: by 2002:a17:903:2589:b0:1d7:85cd:6ed4 with SMTP id jb9-20020a170903258900b001d785cd6ed4mr433730plb.134.1706308602361; Fri, 26 Jan 2024 14:36:42 -0800 (PST) Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id n12-20020a170902d2cc00b001d556872df5si1841991plc.335.2024.01.26.14.36.42 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 14:36:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-40779-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@infradead.org header.s=casper.20170209 header.b=vyGeS6o0; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-40779-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40779-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 763A2283455 for ; Fri, 26 Jan 2024 22:36:40 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 2941648790; Fri, 26 Jan 2024 22:34:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="vyGeS6o0" Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (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 4A86A481A8; Fri, 26 Jan 2024 22:34:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706308456; cv=none; b=JZkBaCxQINLwkqef27ykez4ZwCvu2hN40pwO+EIvKkUbUsbCfXMD0uIenpl+5Q/pdmZp8PUcfJjjSFm5UEgBq9IG3MkXw6ojxmt8/8A91LVa4nTn/p4knYpKNWOYB3zO6/zhrcF8XKeGOpcqlXjuy7VWmOSBpJKqNdBVOO0Yzm8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706308456; c=relaxed/simple; bh=zkqoCMyzx2qjq6i147OphYeumAhy30zhpTYu2BLN/JQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ikkHnUSb7BXYmEGv6SLSqV5y/ueXiFYatBpG/ScWAV3OGH8tWiERYspAIPV7VnanO2XozBq8jkVYds1l3GhaNPCCD1ltMGXVcgoW+PaiFixJpZSMJxWBaipRJ3xzH8rLFUZbSdlnVZTRM4Fsnk4bN+6iJApm+5Oj5sMJKs95cLU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=vyGeS6o0; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=mYAHlDNex9wbOcNfsf4H6GLUDwhTljs91llwoVK/dq0=; b=vyGeS6o07MbDfrCWspAlhgVycZ cN65OoiUOsC1wTLBqHHlBxoo9Vkt/FMvoMZEIu8tHg8K7KA8H9X+SBPiVz5HtVJCWoj0i0/HLJVVk Wbwre1op0p0HQ2pR3v3fCak9tdOGalPQg0r93GnFvDm2ya0CyCEa1e7aqD1m7HsLoicdwK/4hJuo3 HaHxL5mNIGDEOCQ3Jp8J0F96ATfFtg1oczGu4HO/+plhD/MXV4MZwc+fewZJjk5vdx3jPChppdncO QXmaKhZjUCwUlui5xbgWkonFBWEk0lqgKsA9uh9FR2I7cZEh8FrioXNrcfDp4jtdgrE+e7P7WOXE7 AxBlM9dQ==; Received: from willy by casper.infradead.org with local (Exim 4.97.1 #2 (Red Hat Linux)) id 1rTUlx-0000000F3X4-3QSg; Fri, 26 Jan 2024 22:34:06 +0000 Date: Fri, 26 Jan 2024 22:34:05 +0000 From: Matthew Wilcox To: Mathieu Desnoyers Cc: Linus Torvalds , Steven Rostedt , LKML , Linux Trace Devel , Masami Hiramatsu , Christian Brauner , Ajay Kaher , Geert Uytterhoeven , linux-fsdevel Subject: Re: [PATCH] eventfs: Have inodes have unique inode numbers Message-ID: References: <20240126150209.367ff402@gandalf.local.home> <20240126162626.31d90da9@gandalf.local.home> <8547159a-0b28-4d75-af02-47fc450785fa@efficios.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8547159a-0b28-4d75-af02-47fc450785fa@efficios.com> On Fri, Jan 26, 2024 at 05:14:12PM -0500, Mathieu Desnoyers wrote: > I would suggest this straightforward solution to this: > > a) define a EVENTFS_MAX_INODES (e.g. 4096 * 8), > > b) keep track of inode allocation in a bitmap (within a single page), > > c) disallow allocating more than "EVENTFS_MAX_INODES" in eventfs. .. reinventing the IDA?