From: Anatol Pomozov <anatol.pomozov@gmail.com>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: fw@strlen.de, Dmitry Vyukov <dvyukov@google.com>,
Paul McKenney <paulmck@linux.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: seqcount usage in xt_replace_table()
Date: Tue, 8 Jan 2019 16:36:46 -0800 [thread overview]
Message-ID: <CAOMFOmUSttpLyeiRLjxw4rSN0tOiAq1jbwK=kRdCkuOKPOC3Rg@mail.gmail.com> (raw)
In-Reply-To: <20190109000214.GA5907@andrea>
Hello
On Tue, Jan 8, 2019 at 4:02 PM Andrea Parri
<andrea.parri@amarulasolutions.com> wrote:
>
> Hi Anatol,
>
> On Tue, Jan 08, 2019 at 11:33:39AM -0800, Anatol Pomozov wrote:
> > Hello folks,
> >
> > A bit of context what I am doing. I am trying to port KTSAN (Kernel
> > Thread Sanitizer) tool to v4.20. That tool tracks shared data usage
> > and makes sure it is accessed in a thread-safe manner.
>
> Interesting! FYI, some LKMM's maintainers (Paul included) had and
> continued to have some "fun" discussing topics related to "thread-
> safe memory accesses": I'm sure that they'll be very interested in
> such work of yours and eager to discuss your results.
Thread Sanitizer is a great tool to find thread-safety issues with
user-space code. The tool been developed by a team of smart people
from Google [1].
KTSAN is an attempt to bring the same ideas to Linux kernel [2]. A
bunch of work been done there but the project is still at
proof-of-concept point.
I am not a part of Google's dynamic tools team. But I've decided to
pick something to do during the New Year holidays so started porting
KTSAN from v4.2 to v4.20. The work is "almost completed" but I need to
fix a few crashes [3].
[1] https://github.com/google/sanitizers
[2] https://github.com/google/ktsan/wiki
[3] https://github.com/anatol/linux/tree/ktsan_4.20
next prev parent reply other threads:[~2019-01-09 0:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 19:33 seqcount usage in xt_replace_table() Anatol Pomozov
2019-01-08 22:37 ` Florian Westphal
2019-01-10 12:41 ` Peter Zijlstra
2019-01-10 12:53 ` Dmitry Vyukov
2019-01-10 20:18 ` Peter Zijlstra
2019-01-10 14:48 ` Florian Westphal
2019-01-10 20:20 ` Peter Zijlstra
2019-01-10 20:25 ` Peter Zijlstra
2019-01-10 22:29 ` Florian Westphal
2019-01-11 8:34 ` Peter Zijlstra
2019-01-11 14:08 ` Paul E. McKenney
2019-01-10 14:52 ` Paul E. McKenney
2019-01-09 0:02 ` Andrea Parri
2019-01-09 0:36 ` Anatol Pomozov [this message]
2019-01-09 5:35 ` Dmitry Vyukov
2019-01-09 11:24 ` Andrea Parri
2019-01-09 11:55 ` Dmitry Vyukov
2019-01-09 12:11 ` Andrea Parri
2019-01-09 12:29 ` Dmitry Vyukov
2019-01-09 17:10 ` Paul E. McKenney
2019-01-10 8:49 ` Dmitry Vyukov
2019-01-10 12:30 ` Andrea Parri
2019-01-10 12:38 ` Dmitry Vyukov
2019-01-10 12:46 ` Andrea Parri
2019-01-10 13:25 ` Dmitry Vyukov
2019-01-10 14:50 ` Paul E. McKenney
2019-01-10 12:44 ` Peter Zijlstra
2019-01-10 12:54 ` Dmitry Vyukov
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='CAOMFOmUSttpLyeiRLjxw4rSN0tOiAq1jbwK=kRdCkuOKPOC3Rg@mail.gmail.com' \
--to=anatol.pomozov@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=dvyukov@google.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).