On Tue, 5 Nov 2019 at 16:25, Marco Elver <elver@xxxxxxxxxx> wrote: > > On Tue, 5 Nov 2019 at 15:20, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote: > > > > On Tue, Nov 05, 2019 at 12:10:56PM +0100, Marco Elver wrote: > > > On Mon, 4 Nov 2019 at 20:47, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote: > > > > > > > > On Mon, Nov 04, 2019 at 07:41:30PM +0100, Marco Elver wrote: > > > > > On Mon, 4 Nov 2019 at 17:47, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote: > > > > > > > > > > > > On Mon, Nov 04, 2019 at 03:27:36PM +0100, Marco Elver wrote: > > > > > > > This is the patch-series for the Kernel Concurrency Sanitizer (KCSAN). > > > > > > > KCSAN is a sampling watchpoint-based data-race detector. More details > > > > > > > are included in Documentation/dev-tools/kcsan.rst. This patch-series > > > > > > > only enables KCSAN for x86, but we expect adding support for other > > > > > > > architectures is relatively straightforward (we are aware of > > > > > > > experimental ARM64 and POWER support). > > > > > > > > > > > > > > To gather early feedback, we announced KCSAN back in September, and > > > > > > > have integrated the feedback where possible: > > > > > > > http://lkml.kernel.org/r/CANpmjNPJ_bHjfLZCAPV23AXFfiPiyXXqqu72n6TgWzb2Gnu1eA@xxxxxxxxxxxxxx > > > > > > > > > > > > > > We want to point out and acknowledge the work surrounding the LKMM, > > > > > > > including several articles that motivate why data-races are dangerous > > > > > > > [1, 2], justifying a data-race detector such as KCSAN. > > > > > > > [1] https://lwn.net/Articles/793253/ > > > > > > > [2] https://lwn.net/Articles/799218/ > > > > > > > > > > > > > > The current list of known upstream fixes for data-races found by KCSAN > > > > > > > can be found here: > > > > > > > https://github.com/google/ktsan/wiki/KCSAN#upstream-fixes-of-data-races-found-by-kcsan > > > > > > > > > > > > Making this more accessible to more people seems like a good thing. > > > > > > So, for the series: > > > > > > > > > > > > Acked-by: Paul E. McKenney <paulmck@xxxxxxxxxx> > > > > > > > > > > Much appreciated. Thanks, Paul! > > > > > > > > > > Any suggestions which tree this could eventually land in? > > > > > > > > I would guess that Dmitry might have some suggestions. > > > > > > I checked and we're both unclear what the most obvious tree to land in > > > is (the other sanitizers are mm related, which KCSAN is not). > > > > > > One suggestion that comes to my mind is for KCSAN to go through the > > > same tree (rcu?) as the LKMM due to their inherent relationship. Would > > > that make most sense? > > > > It works for me, though you guys have to continue to be the main > > developers. ;-) > > Great, thanks. We did add an entry to MAINTAINERS, so yes of course. :-) > > > I will go through the patches more carefully, and please look into the > > kbuild test robot complaint. > > I just responded to that, it seems to be a sparse problem. > > Thanks, > -- Marco v4 was sent out: http://lkml.kernel.org/r/20191114180303.66955-1-elver@xxxxxxxxxx Thanks, -- Marco
