All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt@linutronix.de>
To: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
	Kurt Kanzenbach <kurt@linutronix.de>
Subject: [PATCH 0/4] rt-tests: deadline: Fix segmentation faults
Date: Thu,  4 Apr 2019 15:48:10 +0200	[thread overview]
Message-ID: <20190404134814.13376-1-kurt@linutronix.de> (raw)

Hi,

the deadline test binaries may crash under certain circumstances.

That seems to be caused by stack buffer overflows. While here, I've noticed that
some memory wasn't free'd. So, added that as well.

Thanks,
Kurt

Kurt Kanzenbach (4):
  rt-tests: cyclicdeadline: fix segmentation fault on close
  rt-tests: cyclicdeadline: add missing free calls
  rt-tests: deadline_tests: fix stack buffer flow
  rt-tests: deadline_test: add missing frees

 src/sched_deadline/cyclicdeadline.c | 4 +++-
 src/sched_deadline/deadline_test.c  | 7 ++++---
 2 files changed, 7 insertions(+), 4 deletions(-)

-- 
2.11.0


             reply	other threads:[~2019-04-04 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 13:48 Kurt Kanzenbach [this message]
2019-04-04 13:48 ` [PATCH 1/4] rt-tests: cyclicdeadline: fix segmentation fault on close Kurt Kanzenbach
2019-04-05 14:33   ` John Kacur
2019-04-04 13:48 ` [PATCH 2/4] rt-tests: cyclicdeadline: add missing free calls Kurt Kanzenbach
2019-04-05 14:34   ` John Kacur
2019-04-04 13:48 ` [PATCH 3/4] rt-tests: deadline_tests: fix stack buffer flow Kurt Kanzenbach
2019-04-05 14:35   ` John Kacur
2019-04-04 13:48 ` [PATCH 4/4] rt-tests: deadline_test: add missing frees Kurt Kanzenbach
2019-04-04 15:13   ` John Kacur
2019-04-04 15:19     ` Kurt Kanzenbach
2019-04-04 15:42       ` John Kacur
2019-04-05 14:36   ` John Kacur

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=20190404134814.13376-1-kurt@linutronix.de \
    --to=kurt@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.