[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1583340277.7365.153.camel@lca.pw>
Date: Wed, 04 Mar 2020 11:44:37 -0500
From: Qian Cai <cai@....pw>
To: Marco Elver <elver@...gle.com>
Cc: paulmck@...nel.org, andreyknvl@...gle.com, glider@...gle.com,
dvyukov@...gle.com, kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org, corbet@....net,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 2/3] kcsan: Update Documentation/dev-tools/kcsan.rst
On Wed, 2020-03-04 at 17:25 +0100, 'Marco Elver' via kasan-dev wrote:
> Selective analysis
> ~~~~~~~~~~~~~~~~~~
> @@ -111,8 +107,8 @@ the below options are available:
>
> * Disabling data race detection for entire functions can be accomplished by
> using the function attribute ``__no_kcsan`` (or ``__no_kcsan_or_inline`` for
> - ``__always_inline`` functions). To dynamically control for which functions
> - data races are reported, see the `debugfs`_ blacklist/whitelist feature.
> + ``__always_inline`` functions). To dynamically limit for which functions to
> + generate reports, see the `DebugFS interface`_ blacklist/whitelist feature.
As mentioned in [1], do it worth mentioning "using __no_kcsan_or_inline for
inline functions as well when CONFIG_OPTIMIZE_INLINING=y" ?
[1] https://lore.kernel.org/lkml/E9162CDC-BBC5-4D69-87FB-C93AB8B3D581@lca.pw/
Powered by blists - more mailing lists