From: Sandy Harris <sandyinchina@gmail.com>
To: stefan.bavendiek@mailbox.org
Cc: kernel-hardening@lists.openwall.com, linux-hardening@vger.kernel.org
Subject: Re: Kernel complexity
Date: Tue, 15 Dec 2020 14:09:30 +0800 [thread overview]
Message-ID: <CACXcFmnrQmQO38yBXh25eD9QgtvjKHTg=oCtJm8Kq6coK+WspA@mail.gmail.com> (raw)
In-Reply-To: <X9UjVOuTgwuQwfFk@mailbox.org>
> I am currently doing a research project that aims to identify risk areas in the kernel by measuring code complexity metrics ...
Another aspect of complexity that might be worth a look is
modularisation, interface definitions for kernel components, etc. One
classic paper is "Ifdef Considered Harmful".
https://www.usenix.org/legacy/publications/library/proceedings/sa92/spencer.pdf
prev parent reply other threads:[~2020-12-15 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 20:08 Kernel complexity stefan.bavendiek
2020-12-12 22:34 ` Jann Horn
2020-12-13 19:04 ` stefan.bavendiek
2020-12-14 6:34 ` Greg KH
2020-12-15 6:09 ` Sandy Harris [this message]
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='CACXcFmnrQmQO38yBXh25eD9QgtvjKHTg=oCtJm8Kq6coK+WspA@mail.gmail.com' \
--to=sandyinchina@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-hardening@vger.kernel.org \
--cc=stefan.bavendiek@mailbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).