[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1907311620010.2747@mbalantz-desktop>
Date: Wed, 31 Jul 2019 16:37:02 -0700 (PDT)
From: Mark Balantzyan <mbalant3@...il.com>
To: Guenter Roeck <linux@...ck-us.net>
cc: Mark Balantzyan <mbalant3@...il.com>, wim@...ux-watchdog.org,
linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org,
Pavel Andrianov <andrianov@...ras.ru>
Subject: Re: [PATCH] watchdog:alim1535_wdt: Fix data race in ali_settimer()
concerning ali_timeout_bits variable.
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
Powered by blists - more mailing lists