linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/5] fixes for rare crashes
Date: Thu,  6 Jul 2017 21:19:45 +0200	[thread overview]
Message-ID: <20170706191950.81268-1-luc.vanoostenryck@gmail.com> (raw)

This series contains some fixes for crashes I found during
some fuzzy-testing.

Most of the reproducers are not at all valid C code and
the crashes occurs very very rarely (a few tens of
crashes after more or less 150 CPU hours of fuzzing)
but I don't see much reasons why more 'normal' uses
could not trigger the crashes.

Sorry for coming with this so late in the release.

Note: I'm not really sure if these patches should be
      included in the release but patch 1/5 is a bit
      different and should be included while patch 5/5
      is only for those who use test-linearize.


The following changes since commit ec3f72e981792a86a9e002471a06d61ecd5c6675:

  bump sparse's version to 0.5.1-rc4 (2017-07-04 08:24:40 -0700)

are available in the git repository at:

  git://github.com/lucvoo/sparse.git fix-fuzzy-crashes

for you to fetch changes up to 2f59acac476c07c4d32b82fb8e214d0d6b8b05fc:

  avoid crash with sym->bb_target == NULL (2017-07-06 20:59:10 +0200)

----------------------------------------------------------------

Luc Van Oostenryck (5):
  do not corrupt ptrlist while killing unreachable BBs
  avoid crash when ep->active is NULL
  avoid crash in rewrite_branch()
  avoid some crashes in add_dominators()
  avoid crash with sym->bb_target == NULL

 flow.c                            |  7 ++++---
 flow.h                            |  2 +-
 linearize.c                       | 14 ++++++++++----
 memops.c                          |  2 ++
 validation/crash-add-doms.c       | 22 ++++++++++++++++++++++
 validation/crash-bb_target.c      | 10 ++++++++++
 validation/crash-ep-active.c      | 17 +++++++++++++++++
 validation/crash-ptrlist.c        | 23 +++++++++++++++++++++++
 validation/crash-rewrite-branch.c | 24 ++++++++++++++++++++++++
 9 files changed, 113 insertions(+), 8 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

-- 
2.13.0


             reply	other threads:[~2017-07-06 19:20 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 19:19 Luc Van Oostenryck [this message]
2017-07-06 19:19 ` [PATCH 1/5] do not corrupt ptrlist while killing unreachable BBs Luc Van Oostenryck
2017-07-07  0:40   ` Christopher Li
2017-07-07  1:18     ` Christopher Li
2017-07-07  1:35       ` Linus Torvalds
2017-07-07  5:15         ` Christopher Li
2017-07-07  8:28           ` Luc Van Oostenryck
2017-07-07  9:06             ` Christopher Li
2017-07-07  9:30               ` Luc Van Oostenryck
2017-07-07  9:54                 ` Christopher Li
2017-07-07 13:18               ` Dibyendu Majumdar
2017-07-07 13:25                 ` Luc Van Oostenryck
2017-07-07 13:29                   ` Dibyendu Majumdar
2017-07-07 13:47                     ` Luc Van Oostenryck
2017-07-08 15:43                       ` Christopher Li
2017-07-07  9:52             ` Luc Van Oostenryck
2017-07-07  6:07         ` Christopher Li
2017-07-07  5:44       ` Luc Van Oostenryck
2017-07-07  6:02         ` Christopher Li
2017-07-07  6:10           ` Luc Van Oostenryck
2017-07-07  6:27             ` Christopher Li
2017-07-07  7:30               ` Luc Van Oostenryck
2017-07-07  9:19           ` Dibyendu Majumdar
2017-07-07  9:26             ` Dibyendu Majumdar
2017-07-07  9:38               ` Luc Van Oostenryck
2017-07-07  9:41                 ` Dibyendu Majumdar
2017-07-07  9:58                   ` Christopher Li
2017-07-07 10:08                     ` Dibyendu Majumdar
2017-07-07 12:54                       ` Christopher Li
2017-07-07 13:01                         ` Dibyendu Majumdar
2017-07-07  9:44             ` Christopher Li
2017-07-07  9:46               ` Dibyendu Majumdar
2017-07-07 10:00                 ` Luc Van Oostenryck
2017-07-07  6:04       ` Luc Van Oostenryck
2017-07-07  6:18         ` Christopher Li
2017-07-07  7:11           ` Luc Van Oostenryck
2017-07-07  8:25             ` Christopher Li
2017-07-07  8:32               ` Luc Van Oostenryck
2017-07-09  9:07   ` Christopher Li
2017-07-09 10:26     ` Luc Van Oostenryck
2017-07-09 14:44       ` Christopher Li
2017-07-09 16:11         ` Luc Van Oostenryck
2017-07-06 19:19 ` [PATCH 2/5] avoid crash when ep->active is NULL Luc Van Oostenryck
2017-07-19 22:20   ` Luc Van Oostenryck
2017-07-20  4:37     ` Christopher Li
2017-07-06 19:19 ` [PATCH 3/5] avoid crash in rewrite_branch() Luc Van Oostenryck
2017-07-19 22:21   ` Luc Van Oostenryck
2017-07-06 19:19 ` [PATCH 4/5] avoid some crashes in add_dominators() Luc Van Oostenryck
2017-07-19 22:22   ` Luc Van Oostenryck
2017-07-06 19:19 ` [PATCH 5/5] avoid crash with sym->bb_target == NULL Luc Van Oostenryck
2017-07-19 22:23   ` Luc Van Oostenryck
2017-07-20 10:57   ` Christopher Li
2017-07-29 12:30     ` Luc Van Oostenryck
2017-07-29 12:49       ` Christopher Li
2017-07-06 19:50 ` [PATCH 0/5] fixes for rare crashes Christopher Li

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=20170706191950.81268-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --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).