From: James Carter <jwcart2@gmail.com>
To: selinux@vger.kernel.org
Cc: nicolas.iooss@m4x.org, James Carter <jwcart2@gmail.com>
Subject: [PATCH 0/5] Fix bugs identified by the secilc-fuzzer
Date: Wed, 28 Apr 2021 16:17:48 -0400 [thread overview]
Message-ID: <20210428201753.282831-1-jwcart2@gmail.com> (raw)
These patches are all related by the fact that the secilc-fuzzer
identified the bugs that led to them. Wherever possible I have
tried to fix all of the issues related to the specific one found.
James Carter (5):
libsepol/cil: Fix instances where an error returns SEPOL_OK
libsepol/cil: Detect degenerate inheritance and exit with an error
libsepol/cil: Check datum in ordered list for expected flavor
libsepol/cil: Check for self-referential loops in sets
libsepol/cil: Return an error if a call argument fails to resolve
libsepol/cil/src/cil_build_ast.c | 3 +
libsepol/cil/src/cil_internal.h | 2 +
libsepol/cil/src/cil_resolve_ast.c | 107 ++++++++++++++++++++---------
libsepol/cil/src/cil_verify.c | 97 ++++++++++++++++++--------
libsepol/cil/src/cil_verify.h | 1 -
5 files changed, 151 insertions(+), 59 deletions(-)
--
2.26.3
next reply other threads:[~2021-04-28 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 20:17 James Carter [this message]
2021-04-28 20:17 ` [PATCH 1/5] libsepol/cil: Fix instances where an error returns SEPOL_OK James Carter
2021-04-28 20:17 ` [PATCH 2/5] libsepol/cil: Detect degenerate inheritance and exit with an error James Carter
2021-04-28 20:17 ` [PATCH 3/5] libsepol/cil: Check datum in ordered list for expected flavor James Carter
2021-04-28 20:17 ` [PATCH 4/5] libsepol/cil: Check for self-referential loops in sets James Carter
2021-05-01 14:33 ` Nicolas Iooss
2021-05-03 13:48 ` James Carter
2021-04-28 20:17 ` [PATCH 5/5] libsepol/cil: Return an error if a call argument fails to resolve James Carter
2021-05-04 20:07 ` [PATCH 0/5] Fix bugs identified by the secilc-fuzzer James Carter
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=20210428201753.282831-1-jwcart2@gmail.com \
--to=jwcart2@gmail.com \
--cc=nicolas.iooss@m4x.org \
--cc=selinux@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