Files
fips/testing/check-shellcheck.sh
Johnathan Corgan 26cfb4fad3 Merge maint into master: the lookup forward limiter's per-origin limits, the peer ACL and Nostr traversal docs, the root-only test script, and the narrow-path TCP fixes
The peer ACL changelog entry joins master's existing Links and
transports section under Security rather than opening a second one.

testing/root-tests.sh carries master's filters rather than maint's, in
two groups: the TUN warning, DNS responder and gateway mesh tests (18),
and the Linux TUN namespace tests (13). It needs ip, nft and sysctl
here, and its probe also writes a sysctl inside the namespace, as four
of the TUN tests do, so a container with a read-only /proc/sys is
reported as such.

GitHub's Linux job ran those groups as two steps; they are now one step
that runs the script under sudo. ci-local.sh takes --root-tests or
FIPS_CI_ROOT_TESTS=1 alongside --baremetal and --slow-tests, and --rerun
rejects both forms. The README section sits beside the known-defect
lane, and the comments that said which runners run these tests now name
the script.

The held-SYN re-clamp and ingress fragmentation for paths under 1280
are ported rather than taken as written: on master the IPv6 adapter
hands the node compressed datagrams and the node judges them in
handle_datagram.

- The fragmenter moves to src/ipv6tun/ipv6_frag.rs with its body and
  tests unchanged, listed as one of the adapter's decision modules.
- outbound.rs gains can_split, split and reclamp, pure functions that
  rebuild a held datagram's packet, fragment it or clamp its SYN, and
  compress the result. mss.rs gains flow_ceiling, the per-flow MSS
  ceiling the TUN reader and the release-time re-clamp now share.
- handle_datagram lets a datagram over the node-wide limit or an
  established session's path MTU carry on whole when it can be
  fragmented. The established send and the flush of held datagrams go
  through send_tun_packet, which sends a datagram whole or as fragments
  by the smaller of the node's own limit and the session's path MTU, and
  the flush clamps a held SYN again from the node's own path MTU map.
- A Packet Too Big for a packet over 1280 on a path under 1280 reports
  1280, both for a datagram the node refuses and for one the adapter
  answers itself.
- The new node tests are ported to master's TUN taps and compressed held
  payloads. The two existing Packet Too Big tests that now use a
  Hop-by-Hop header give it a real length, since master's ICMPv6 builder
  does not answer a packet whose extension headers run past its end.
  The host-link tests of refusals send a packet with a Hop-by-Hop header
  where they mean a packet that is refused rather than fragmented, and
  one of them also checks that a fragmentable oversized packet to a key
  the node cannot resolve is told no route.

The IPv6 adapter design document now says that on this structure the
node decides fragmentation at its two refusal sites and splits a
datagram where it sends it, that it clamps a held SYN again from its
own path MTU map when it releases the datagrams it held, and that both
apply to an app-owned TUN because the node holds and releases the
datagrams of either path. It also names the functions an app-owned
TUN's packets pass through on this structure, Handles::outbound and
handle_datagram, and the MTU document says it is the ingress node that
fragments.
2026-10-29 00:03:54 +00:00

164 lines
6.9 KiB
Bash
Executable File

#!/bin/bash
# ── OpenWrt shell-script lint guard ─────────────────────────────────────────
# Runs shellcheck over the shell scripts the OpenWrt packages ship, over
# .github/scripts/install-nak.sh, which the OpenWrt Package workflow runs to
# fetch its publishing tool, over that workflow's Blossom upload helper and
# its test (.github/scripts/blossom-upload.sh, test-blossom-upload.sh), over
# testing/build-core-baremetal.sh, which both CI runners run, over the
# cross-target compile check that ci-local.sh runs (testing/cross-check/),
# over the crate publication check that crate.yml runs
# (testing/check-crate.sh), over the FreeBSD package's upgrade test
# (packaging/freebsd/test-upgrade.sh), which the FreeBSD Package workflow runs
# in its VM, and over the root-only test runner that ci.yml and ci-local.sh
# run and the internal builder is to run (testing/root-tests.sh).
#
# This is the one copy of that lint. The OpenWrt Package workflow calls it
# after building each .ipk, and ci.yml and ci-local.sh call it too, because
# that workflow runs only on trunk pushes, tags and pull requests: without the
# other two, a finding in a script edited on a topic branch first shows up
# after the branch has reached a trunk.
#
# What is checked, and how:
# * Every script under packaging/openwrt-ipk/files/ and the maintainer
# scripts under packaging/openwrt-ipk/scripts/, as POSIX sh. Both the .ipk
# and the .apk package take their payload and maintainer scripts from these
# two directories (build-apk.sh wraps the maintainer scripts with one
# header line, which is not linted separately); the SDK feed Makefile ships
# preinst as well. On a router they run under busybox ash.
# * packaging/freebsd/test-upgrade.sh as POSIX sh with the same
# exclusions; it runs under FreeBSD's sh, which supports `local` too.
# * install-nak.sh, blossom-upload.sh, test-blossom-upload.sh,
# keep-pinned-toolchain.sh, build-core-baremetal.sh, the three
# testing/cross-check/ scripts, testing/check-crate.sh and
# testing/root-tests.sh as bash, with
# no exclusions. They are CI scripts, not shipped ones, and the sh
# exclusion set below misfires on bash.
#
# The sh exclusions, with reason:
# SC1008 the init scripts' `#!/bin/sh /etc/rc.common` shebang, an
# interpreter line the linter does not recognise.
# SC2317 rc.common's start_service/stop_service/reload_service hooks,
# which nothing in the file itself calls.
# SC2034 the init scripts' USE_PROCD, START, STOP, EXTRA_COMMANDS and
# EXTRA_HELP, which rc.common reads rather than the script.
# SC3043 `local`, which POSIX leaves undefined and ash supports.
#
# Every sh-family script in those two directories must be on the list below. A
# new one that is not fails the guard, so a script added to the package is not
# silently left unlinted.
#
# Exit 0 = clean. Exit 1 = a finding, a listed script missing, or a shipped
# script not on the list. Exit 2 = the guard could not run (shellcheck or git
# missing, or shellcheck could not process a file); never treated as a pass.
# ─────────────────────────────────────────────────────────────────────────────
set -uo pipefail
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
cd "$PROJECT_ROOT" || { echo "check-shellcheck: cannot cd to $PROJECT_ROOT" >&2; exit 2; }
IPK=packaging/openwrt-ipk
SH_EXCLUDE=SC1008,SC2317,SC2034,SC3043
SH_TARGETS=(
"$IPK/files/etc/init.d/fips"
"$IPK/files/etc/init.d/fips-gateway"
"$IPK/files/etc/uci-defaults/90-fips-setup"
"$IPK/files/usr/bin/fips-mesh-setup"
"$IPK/files/usr/bin/fips-ap-setup"
"$IPK/scripts/preinst"
"$IPK/scripts/postinst"
"$IPK/scripts/prerm"
"packaging/freebsd/test-upgrade.sh"
)
BASH_TARGETS=(
".github/scripts/install-nak.sh"
".github/scripts/blossom-upload.sh"
".github/scripts/test-blossom-upload.sh"
".github/scripts/keep-pinned-toolchain.sh"
"testing/build-core-baremetal.sh"
"testing/cross-check/check.sh"
"testing/check-crate.sh"
"testing/root-tests.sh"
"testing/cross-check/zig-cc"
"testing/cross-check/zig-ar"
)
if ! command -v shellcheck >/dev/null 2>&1; then
echo "check-shellcheck: shellcheck not found; cannot lint the shell scripts" >&2
echo "check-shellcheck: install it with 'apt-get install shellcheck'" >&2
exit 2
fi
if ! command -v git >/dev/null 2>&1; then
echo "check-shellcheck: git not found; cannot list the shipped scripts" >&2
exit 2
fi
shellcheck --version | sed -n 's/^version: /check-shellcheck: shellcheck /p'
findings=0
broken=0
# ── Completeness: every shipped sh-family script is on the list ─────────────
shipped=$(git ls-files -- "$IPK/files" "$IPK/scripts") || {
echo "check-shellcheck: git ls-files failed, refusing to pass" >&2
exit 2
}
if [[ -z "$shipped" ]]; then
echo "check-shellcheck: git ls-files found nothing under $IPK, refusing to pass" >&2
exit 2
fi
while IFS= read -r f; do
# A tracked file deleted from the working tree: if listed, the lint below
# reports it missing; if not, there is nothing to ship.
[[ -f "$f" ]] || continue
head -n 1 "$f" | grep -qE '^#![[:space:]]*[^[:space:]]*/(env[[:space:]]+)?(ba|a|da)?sh([[:space:]]|$)' || continue
listed=0
for t in "${SH_TARGETS[@]}"; do
[[ "$t" == "$f" ]] && { listed=1; break; }
done
if [[ $listed -eq 0 ]]; then
echo "FAIL: $f is a shipped shell script missing from SH_TARGETS in $0"
findings=1
fi
done <<< "$shipped"
# ── Lint ─────────────────────────────────────────────────────────────────────
lint() {
# lint <file> <shellcheck args...>: one file; sets findings or broken.
local f="$1" rc=0
shift
if [[ ! -f "$f" ]]; then
echo "FAIL: missing $f"
findings=1
return 0
fi
echo "==> shellcheck $* $f"
shellcheck "$@" "$f" || rc=$?
case $rc in
0) echo " PASS" ;;
1) echo " FAIL"; findings=1 ;;
*) echo " shellcheck exited $rc: could not check $f"; broken=1 ;;
esac
return 0
}
for f in "${SH_TARGETS[@]}"; do
lint "$f" --shell=sh --exclude="$SH_EXCLUDE"
done
for f in "${BASH_TARGETS[@]}"; do
lint "$f" --shell=bash
done
total=$(( ${#SH_TARGETS[@]} + ${#BASH_TARGETS[@]} ))
if [[ $broken -ne 0 ]]; then
echo "shellcheck could not check every script; refusing to pass"
exit 2
fi
if [[ $findings -ne 0 ]]; then
echo "shellcheck FAILED"
exit 1
fi
echo "shellcheck PASS ($total scripts: ${#SH_TARGETS[@]} as sh, ${#BASH_TARGETS[@]} as bash)"
exit 0