From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org,
Michael Stefaniuc <mstefani@mykolab.com>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH v3 0/7] fixes for rare issues
Date: Mon, 31 Jul 2017 22:36:17 +0200 [thread overview]
Message-ID: <20170731203624.58971-1-luc.vanoostenryck@gmail.com> (raw)
This series contains some fixes for crashes I found during
some fuzzy-testing, as well as for some infinite loops
that may happen during simplification.
Patch 3 is quite fundamental for all BB simplifications.
I won't bet this is all perfect now but at least the change
make a lot of sense and I'm confident that the situation is
now a lot saner.
It passes all functional tests (regressions test & kernel check),
it should be fine when used on the Wine code too.
Changes since v3:
- change the way kill_unreachable_bbs() is called (patch 1)
- add fix for the infinite simplification loops (patch 2 & 3)
This series is also available at:
git://github.com/lucvoo/sparse.git fix-fuzzy-crashes-v3
----------------------------------------------------------------
Luc Van Oostenryck (7):
fix ptrlist corruption while killing unreachable BBs
fix infinite simplification loops
fix BB dependencies on phi-nodes
fix crash when ep->active is NULL
fix crash in rewrite_branch()
fix some crashes in add_dominators()
fix crash with sym->bb_target == NULL
cse.c | 2 ++
flow.c | 38 ++++++++++++++++++--------------------
linearize.c | 17 +++++++++++------
memops.c | 2 ++
simplify.c | 9 +++++++++
validation/crash-add-doms.c | 22 ++++++++++++++++++++++
validation/crash-bb_target.c | 10 ++++++++++
validation/crash-ep-active.c | 12 ++++++++++++
validation/crash-ptrlist.c | 23 +++++++++++++++++++++++
validation/crash-rewrite-branch.c | 24 ++++++++++++++++++++++++
validation/crazy02-not-so.c | 18 ++++++++++++++++++
validation/infinite-loop02.c | 11 +++++++++++
validation/infinite-loop03.c | 16 ++++++++++++++++
13 files changed, 178 insertions(+), 26 deletions(-)
create mode 100644 validation/crash-add-doms.c
create mode 100644 validation/crash-bb_target.c
create mode 100644 validation/crash-ep-active.c
create mode 100644 validation/crash-ptrlist.c
create mode 100644 validation/crash-rewrite-branch.c
create mode 100644 validation/infinite-loop02.c
create mode 100644 validation/infinite-loop03.c
next reply other threads:[~2017-07-31 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 20:36 Luc Van Oostenryck [this message]
2017-07-31 20:36 ` [PATCH v3 1/7] fix ptrlist corruption while killing unreachable BBs Luc Van Oostenryck
2017-07-31 21:41 ` Christopher Li
2017-07-31 22:10 ` Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 2/7] fix infinite simplification loops Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 3/7] fix BB dependencies on phi-nodes Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 4/7] fix crash when ep->active is NULL Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 5/7] fix crash in rewrite_branch() Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 6/7] fix some crashes in add_dominators() Luc Van Oostenryck
2017-07-31 20:36 ` [PATCH v3 7/7] fix crash with sym->bb_target == NULL Luc Van Oostenryck
2017-07-31 21:01 ` [PATCH v3 0/7] fixes for rare issues Christopher Li
2017-07-31 21:54 ` Luc Van Oostenryck
2017-07-31 22:34 ` Luc Van Oostenryck
2017-07-31 22:42 ` Luc Van Oostenryck
2017-08-01 20:46 ` Luc Van Oostenryck
2017-08-01 21:49 ` Christopher Li
2017-08-01 22:10 ` Luc Van Oostenryck
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=20170731203624.58971-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mstefani@mykolab.com \
--cc=sparse@chrisli.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 NNTP newsgroup(s).