From: Qian Cai <cai@lca.pw>
To: Marco Elver <elver@google.com>
Cc: paulmck@kernel.org, andreyknvl@google.com, glider@google.com,
dvyukov@google.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/3] kcsan: Update Documentation/dev-tools/kcsan.rst
Date: Wed, 04 Mar 2020 11:44:37 -0500 [thread overview]
Message-ID: <1583340277.7365.153.camel@lca.pw> (raw)
In-Reply-To: <20200304162541.46663-2-elver@google.com>
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/
next prev parent reply other threads:[~2020-03-04 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 16:25 [PATCH 1/3] kcsan: Fix a typo in a comment Marco Elver
2020-03-04 16:25 ` [PATCH 2/3] kcsan: Update Documentation/dev-tools/kcsan.rst Marco Elver
2020-03-04 16:44 ` Qian Cai [this message]
2020-03-04 16:57 ` Marco Elver
2020-03-05 14:24 ` Marco Elver
2020-03-04 16:25 ` [PATCH 3/3] kcsan: Update API documentation in kcsan-checks.h Marco Elver
2020-03-04 17:15 ` [PATCH 1/3] kcsan: Fix a typo in a comment Paul E. McKenney
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=1583340277.7365.153.camel@lca.pw \
--to=cai@lca.pw \
--cc=andreyknvl@google.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.