From: Mark Balantzyan <mbalant3@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Balantzyan <mbalant3@gmail.com>,
wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pavel Andrianov <andrianov@ispras.ru>
Subject: Re: [PATCH] watchdog:alim1535_wdt: Fix data race in ali_settimer() concerning ali_timeout_bits variable.
Date: Wed, 31 Jul 2019 16:37:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1907311620010.2747@mbalantz-desktop> (raw)
In-Reply-To: <20190731192410.GA4935@roeck-us.net>
Hi Guenter, all,
I don't really understand this focus on fixing theoretic/irrelevant
race conditions in drivers which no one uses anymore. Maybe someone
can enlighten me ?
In conjunction with linuxtesting.org and The Linux Foundation, I've been
enlisted to test and work on helping to test tools they use for
reliability testing of linux-based systems. In particular, two tools,
RaceHound (whose command is 'lines2insns' and which isolates race
conditions in kernel modules) and Klever, which is browser-based, are
under continual development by the Center and I aim to help them improve
their throughput by aiding in investigating where, in the automated nature
particularly of Klever (requiring considerable configuration as well),
there may areas to improve.
Hence, yes, a large amount of our findings result in manifesting as
theoretical and possible only, but relevant to improving the tools
nonetheless.
Hope that helps with the 'enlightening' :), regards,
Mark
next prev parent reply other threads:[~2019-07-31 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 15:52 [PATCH] watchdog:alim1535_wdt: Fix data race in ali_settimer() concerning ali_timeout_bits variable. variable Mark Balantzyan
2019-07-18 16:34 ` Guenter Roeck
2019-07-31 16:17 ` [PATCH] watchdog:alim1535_wdt: Fix data race in ali_settimer() concerning ali_timeout_bits variable Mark Balantzyan
2019-07-31 16:43 ` Guenter Roeck
2019-07-31 17:04 ` Mark Balantzyan
2019-07-31 18:23 ` Mark Balantzyan
2019-07-31 19:24 ` Guenter Roeck
2019-07-31 23:37 ` Mark Balantzyan [this message]
[not found] <CACV1r+a4bz+5L_AkYJ0NXkhwarx30=W3MQ20ur1A4Z-zEOE=FA@mail.gmail.com>
2019-07-22 16:38 ` Guenter Roeck
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=alpine.DEB.2.21.1907311620010.2747@mbalantz-desktop \
--to=mbalant3@gmail.com \
--cc=andrianov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.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 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).