From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] firmware scanning for features?
Date: Fri, 3 Dec 2021 08:20:40 -0800 [thread overview]
Message-ID: <CAA93jw7Ea8pM_HbFUQ4FWy5scECi3KjAWe-aMhrRiqqUH2WrHg@mail.gmail.com> (raw)
I imagine firmware scanning has been raised to a high art at this
point, mostly, looking for vulnerabilities, but it occurred to me this
morning that it would be possible to scan for a given feature's code
pattern (in our perpetual case, looking for fq-codel, bql, and cake),
and whether they were in by default (module loader, symbol tables,
qdisc_create_dflt). I imagine recognizable patterns, lacking a symbol
table, would include the invsqrt approximation, in cake's case the
invsqrt table, stuff that manipulates the ecn bits, and so on.
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2021-12-03 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7Ea8pM_HbFUQ4FWy5scECi3KjAWe-aMhrRiqqUH2WrHg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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