From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Blaise Boscaccy <bboscaccy@linux.microsoft.com>
Subject: Re: [PATCH] oid_registry: allow arbitrary size OIDs
Date: Tue, 25 Nov 2025 20:35:14 +0000 [thread overview]
Message-ID: <3954440.1764102914@warthog.procyon.org.uk> (raw)
In-Reply-To: <20251125103325.561b88615d1f0a21ddc6262d@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> How big a problem is this in shipped kernels? Should we backport it?
Not really much of a problem. The OIDs that get compiled are all listed in
include/linux/oid_registry.h. External forces can't add new ones dynamically.
David
next prev parent reply other threads:[~2025-11-25 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 18:19 James Bottomley
2025-11-25 18:33 ` Andrew Morton
2025-11-25 20:33 ` David Howells
2025-11-25 22:12 ` James Bottomley
2025-11-25 20:35 ` David Howells [this message]
2025-11-25 22:03 ` James Bottomley
2025-11-26 19:22 ` [PATCH v2 1/1] " James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3954440.1764102914@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®