From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 4CC37330B21 for ; Tue, 25 Nov 2025 18:33:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764095608; cv=none; b=MTwuxGNjDfVxJ0AmG73OK6ArqSvvBzJm7nl8FfLrd94BSxB9rR7/qtTe3jvR76guwtFl+gPMPi80EDLvoZQ0KxV+iJKmo6OTIweGkZYnQLMsu+ZEwv1YzND7kWMKa3wvatVcfKVHwa2GSbLWvWjdvTvt2kx45+uXepT6354ZyXQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764095608; c=relaxed/simple; bh=qAv0wSwKJ+FZyip7PwLKNKqiWU/rKXYJCPFJ2GOOtbU=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=bfdTL6eOcLjPPcWAk8d/Vsw44fYUFswT6FedXkOjiXBfYs6BnkmzuVNwZtdpfFvpl37UHNfSBD1jo5DMGz9PXwp4DsKmYe7rnWtiaPFdxsDRjEr3Pn2xe/yrwDhcQBM5R/hEiPGULPTgvNqNIIr6+o5Ok5p5rN7MnzTKiCOIvAc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=y0XZq8+W; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="y0XZq8+W" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 45AF1C116B1; Tue, 25 Nov 2025 18:33:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1764095606; bh=qAv0wSwKJ+FZyip7PwLKNKqiWU/rKXYJCPFJ2GOOtbU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=y0XZq8+WI4DOv2iwwA8NB6a2P+awnElIUtPsWnGiGXbAfWeKwurcTX7OINDulJYXr SLF7DxY6OzfqC0Ol2fODlGlEDA0e2heS4Vm7Ul1OoVeW8kPb4tJAI7afBxjHIcSh6o M28ThUtMqioyM3LqEZXtpIr6yMJBD6H8F0xW/OTY= Date: Tue, 25 Nov 2025 10:33:25 -0800 From: Andrew Morton To: James Bottomley Cc: linux-kernel , David Howells , Blaise Boscaccy Subject: Re: [PATCH] oid_registry: allow arbitrary size OIDs Message-Id: <20251125103325.561b88615d1f0a21ddc6262d@linux-foundation.org> In-Reply-To: <833c858cd74533203b43180208734b84f1137af0.camel@HansenPartnership.com> References: <833c858cd74533203b43180208734b84f1137af0.camel@HansenPartnership.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) 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-Transfer-Encoding: 7bit On Tue, 25 Nov 2025 13:19:56 -0500 James Bottomley wrote: > The current OID registry parser uses 64 bit arithmetic which limits us > to supporting 64 bit or smaller OIDs. This isn't usually a problem > except that it prevents us from representing the 2.25. prefix OIDs > which are the OID representation of UUIDs and have a 128 bit number > following the prefix. Rather than import not often used perl > arithmetic modules, replace the current perl 64 bit arithmetic with a > callout to bc, which is arbitrary precision. > How big a problem is this in shipped kernels? Should we backport it?