[<prev] [next>] [day] [month] [year] [list]
Message-ID: <563B9CAC.4080500@yandex.ru>
Date:	Thu, 5 Nov 2015 21:15:08 +0300
From:	Evgenii Shatokhin <eugene.shatokhin@...dex.ru>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [ANNOUNCE] RaceHound 1.1
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
