From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Anatol Pomozov <anatol.pomozov@gmail.com>,
Florian Westphal <fw@strlen.de>,
Paul McKenney <paulmck@linux.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrey Konovalov <andreyknvl@google.com>,
Alan Stern <stern@rowland.harvard.edu>,
Luc Maranget <luc.maranget@inria.fr>,
Will Deacon <will.deacon@arm.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: seqcount usage in xt_replace_table()
Date: Wed, 9 Jan 2019 13:11:26 +0100 [thread overview]
Message-ID: <20190109121126.GA7141@andrea> (raw)
In-Reply-To: <CACT4Y+YAr1XuwAy1qRL678VHZjzsbAQ05o1zoN9ZfC0muYzK8g@mail.gmail.com>
On Wed, Jan 09, 2019 at 12:55:27PM +0100, Dmitry Vyukov wrote:
> On Wed, Jan 9, 2019 at 12:24 PM Andrea Parri
> <andrea.parri@amarulasolutions.com> wrote:
> >
> > On Tue, Jan 08, 2019 at 04:36:46PM -0800, Anatol Pomozov wrote:
> > > 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.
> >
> > Yes, I have been aware of these tools since at least ;-)
> >
> > https://groups.google.com/forum/#!msg/ktsan/bVZ1c6H2NE0/Dxrw55bfBAAJ
> >
> >
> > >
> > > 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].
> >
> > I guess my first reaction would remain
> >
> > "it's kind of hard (to use an euphemism) to review 7,582 additions
> > or so for a data race detector without a clear/an accepted (by the
> > community) notion of data race..."
>
> Tsan's notion of a data race is basically the C/C++'s notion:
> concurrent/unsynchronized non-atomic access in different threads at
> least one of which is a write.
Yeah, I think that this notion needs to be detailed, discussed,
documented, and discussed again. ;-)
> Tremendous (for such a project) benefits of automatic data race
> detection is a good motivation to finally agree on and accept a
> practically useful notion of a data race.
Agreed.
Andrea
next prev parent reply other threads:[~2019-01-09 12:12 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
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 [this message]
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=20190109121126.GA7141@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=anatol.pomozov@gmail.com \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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).