public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgenii Shatokhin <eugene.shatokhin@yandex.ru>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] RaceHound 1.1
Date: Thu, 5 Nov 2015 21:15:08 +0300	[thread overview]
Message-ID: <563B9CAC.4080500@yandex.ru> (raw)

RaceHound 1.1 has been released.

This is a data race detector for the Linux kernel 3.14 or newer, on x86. 
It checks the kernel code in runtime and although it may miss some 
races, it produces no false alarms.

It can be used to confirm the potential races found by other tools, or 
can be used standalone to "sweep" through a given area of code looking 
if data races happen there.

RaceHound relies on Kprobes and hardware breakpoints to detect the 
conflicting memory accesses.

Changes since v.1.0
Enhancements:
* The kernel-mode part of RaceHound now reports the events ("breakpoint 
hit", "race found") to the user space via a file in debugfs that can be 
polled. The following two new scripts use this.
* examples/events.py Python script simply outputs the current events to 
stdout.
* examples/check_apps.py script allows to monitor a number of locations 
in the code, it adjusts the set of monitored locations depending on how 
often they are executed, to keep the overhead lower.

Bug fixes:
* lines2insns did not show all instructions in some cases 
(https://github.com/winnukem/racehound/issues/7)
* A race between removal of a BP and processing of that BP was fixed - 
yes, RaceHound had races too ;-)
* a few smaller fixes.

Downloads: https://github.com/winnukem/racehound/releases/tag/1.1

Details, build instructions, etc: https://github.com/winnukem/racehound.

Regards,
Evgenii

                 reply	other threads:[~2015-11-05 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=563B9CAC.4080500@yandex.ru \
    --to=eugene.shatokhin@yandex.ru \
    --cc=linux-kernel@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