Netdev List
 help / color / mirror / Atom feed
From: Rachel Menge <rachelmenge@linux.microsoft.com>
To: stable@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Request backport of bf5a54bc0e3d to 6.18.y
Date: Fri, 9 Oct 2026 15:36:42 -0700	[thread overview]
Message-ID: <899bd843-fd19-418e-8913-91bfb6e760a2@linux.microsoft.com> (raw)

Hi stable team,

Please consider applying the following upstream commit to 6.18.y:

bf5a54bc0e3d8962474fcd611f1266eba036232f
doc/netlink: netlink-raw: Add max check

The 6.18.y tree contains these related changes:

2fd0880f0272 ("net: reject oversized tx_queue_len at netlink parse time")
982c7f66c041 ("neighbour: Enforce min/max to NDTPA_INTERVAL_PROBE_TIME_MS.")

Those changes add checks.max to the rt-link.yaml and rt-neigh.yaml
Netlink specifications. However, the 6.18.y version of
Documentation/netlink/netlink-raw.yaml neither defines len-or-limit nor
permits checks.max.

I found this while building YNL from v6.18.55. I reproduced the failure
against the unmodified v6.18.55 tag with:

   make -C tools/net/ynl/generated rt-link-user.h

YNL code generation fails JSON schema validation because the rt-link and
rt-neigh specifications use checks.max while netlink-raw.yaml rejects that
property:

   jsonschema.exceptions.ValidationError:
   Additional properties are not allowed ('max' was unexpected)

The requested upstream commit updates only the build-time YAML schema. It
does not change kernel runtime behavior.

I also checked 6.1.y, 6.6.y, 6.12.y, and 6.19.y. Those branches do not
contain the rt-link.yaml and rt-neigh.yaml checks.max additions that create
this mismatch, so this request is limited to 6.18.y.

Thanks,
Rachel Menge

             reply	other threads:[~2026-10-09 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 22:36 Rachel Menge [this message]
2026-10-10  3:59 ` Request backport of bf5a54bc0e3d to 6.18.y Anton Danilov
2026-10-11 16:48 ` Sasha Levin

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=899bd843-fd19-418e-8913-91bfb6e760a2@linux.microsoft.com \
    --to=rachelmenge@linux.microsoft.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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