Re: [PATCH v3] kcsan: Add option for verbose reporting

[Qian Cai]

> On Apr 6, 2020, at 3:51 PM, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote:
> 
> On Mon, Apr 06, 2020 at 09:45:44AM -0400, Qian Cai wrote:
>> 
>> 
>>> On Apr 6, 2020, at 9:35 AM, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote:
>>> 
>>> It goes back in in seven days, after -rc1 is released.  The fact that
>>> it was there last week was a mistake on my part, and I did eventually
>>> get my hand slapped for it.  ;-)
>>> 
>>> In the meantime, if it would help, I could group the KCSAN commits
>>> on top of those in -tip to allow you to get them with one "git pull"
>>> command.
>> 
>> Testing Linux-next for a week without that commit with KCSAN is a torture, so please do that if that is not much work. Otherwise, I could manually cherry-pick the commit myself after fixing all the offsets.
> 
> Just to confirm, you are interested in this -rcu commit, correct?
> 
> 2402d0eae589 ("kcsan: Add option for verbose reporting")
> 
> This one and the following are directly on top of the KCSAN stack
> that is in -tip and thus -next:
> 
> 48b1fc1 kcsan: Add option to allow watcher interruptions
> 2402d0e kcsan: Add option for verbose reporting
> 44656d3 kcsan: Add current->state to implicitly atomic accesses
> e7b3410 kcsan: Fix a typo in a comment
> e7325b7 kcsan: Update Documentation/dev-tools/kcsan.rst
> 1443b8c kcsan: Update API documentation in kcsan-checks.h
> 
> These are on top of this -tip commit:
> 
> f5d2313bd3c5 ("kcsan, trace: Make KCSAN compatible with tracing")
> 
> You can pull them in via the kcsan-dev.2020.03.25a branch if you wish.

Great! That should be enough food for me to survive for this week.