From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrea Parri <andrea.parri@amarulasolutions.com>,
Mark Rutland <mark.rutland@arm.com>,
Dhaval Giani <dhaval.giani@gmail.com>,
Sasha Levin <alexander.levin@microsoft.com>,
shuah <shuah@kernel.org>, Kevin Hilman <khilman@baylibre.com>,
Tim Bird <tbird20d@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"Carpenter,Dan" <dan.carpenter@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
gustavo padovan <gustavo.padovan@collabora.co.uk>,
knut omang <knut.omang@oracle.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: Linux Testing Microconference at LPC
Date: Thu, 23 May 2019 07:03:56 -0700 [thread overview]
Message-ID: <20190523140356.GN28207@linux.ibm.com> (raw)
In-Reply-To: <CACT4Y+aj8i0VNad91F-QkHNsXYXUFrYF+j=wnG-USzfQfoD55A@mail.gmail.com>
On Wed, May 22, 2019 at 05:52:17PM +0200, Dmitry Vyukov wrote:
> On Sun, May 12, 2019 at 2:40 AM Andrea Parri
> <andrea.parri@amarulasolutions.com> wrote:
> >
> > On Tue, Apr 23, 2019 at 11:22:50AM +0100, Mark Rutland wrote:
> > > On Thu, Apr 11, 2019 at 10:37:51AM -0700, Dhaval Giani wrote:
> > > > Hi Folks,
> > > >
> > > > This is a call for participation for the Linux Testing microconference
> > > > at LPC this year.
> > > >
> > > > For those who were at LPC last year, as the closing panel mentioned,
> > > > testing is probably the next big push needed to improve quality. From
> > > > getting more selftests in, to regression testing to ensure we don't
> > > > break realtime as more of PREEMPT_RT comes in, to more stable distros,
> > > > we need more testing around the kernel.
> > > >
> > > > We have talked about different efforts around testing, such as fuzzing
> > > > (using syzkaller and trinity), automating fuzzing with syzbot, 0day
> > > > testing, test frameworks such as ktests, smatch to find bugs in the
> > > > past. We want to push this discussion further this year and are
> > > > interested in hearing from you what you want to talk about, and where
> > > > kernel testing needs to go next.
> > >
> > > I'd be interested to discuss what we could do with annotations and
> > > compiler instrumentation to make the kernel more amenable to static and
> > > dynamic analysis (and to some extent, documenting implicit
> > > requirements).
> > >
> > > One idea that I'd like to explore in the context of RT is to annotate
> > > function signatures with their required IRQ/preempt context, such that
> > > we could dynamically check whether those requirements were violated
> > > (even if it didn't happen to cause a problem at that point in time), and
> > > static analysis would be able to find some obviously broken usage. I had
> > > some rough ideas of how to do the dynamic part atop/within ftrace. Maybe
> > > there are similar problems elsewhere.
> > >
> > > I know that some clang folk were interested in similar stuff. IIRC Nick
> > > Desaulniers was interested in whether clang's thread safety analysis
> > > tooling could be applied to the kernel (e.g. based on lockdep
> > > annotations).
> >
> > FWIW, I'd also be interested in discussing these developments.
> >
> > There have been several activities/projects related to such "tooling"
> > (thread safety analysis) recently: I could point out the (brand new)
> > Google Summer of Code "Applying Clang Thread Safety Analyser to Linux
> > Kernel" project [1] and (for the "dynamic analysis" side) the efforts
> > to revive the Kernel Thread sanitizer [2]. I should also mention the
> > efforts to add (support for) "unmarked" accesses and to formalize the
> > notion of "data race" in the memory consistency model [3].
> >
> > So, again, I'd welcome a discussion on these works/ideas.
> >
> > Thanks,
> > Andrea
>
> I would be interested in discussing all of this too: thread safety
> annotations, ktsan, unmarked accesses.
Sounds like a great discussion! Might this fit into Sasha Levin's
and Dhaval Giani's proposed Testing & Fuzzing MC?
Thanx, Paul
next prev parent reply other threads:[~2019-05-23 14:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 17:37 Linux Testing Microconference at LPC Dhaval Giani
2019-04-18 10:22 ` Gustavo Padovan
2019-04-18 13:26 ` Steven Rostedt
2019-04-22 7:12 ` Guillaume Tucker
2019-04-23 8:37 ` Knut Omang
2019-04-23 10:22 ` Mark Rutland
2019-05-12 0:40 ` Andrea Parri
2019-05-22 15:52 ` Dmitry Vyukov
2019-05-23 14:03 ` Paul E. McKenney [this message]
2019-04-25 13:37 ` Veronika Kabatova
2019-04-26 21:02 ` Tim Bird
2019-05-16 0:39 ` Sasha Levin
2019-05-16 0:51 ` Tim.Bird
2019-05-22 16:04 ` Dmitry Vyukov
2019-05-22 16:07 ` Dhaval Giani
2019-05-22 15:48 ` Dmitry Vyukov
2019-05-23 0:07 ` Tim.Bird
2019-05-23 6:49 ` Dmitry Vyukov
2019-05-15 22:44 ` shuah
2019-05-15 23:19 ` Brendan Higgins
2019-05-16 0:36 ` Sasha Levin
2019-05-22 21:02 ` Brendan Higgins
2019-05-23 0:58 ` Steven Rostedt
2019-05-23 1:00 ` Steven Rostedt
2019-05-23 4:54 ` Knut Omang
2019-06-03 8:59 ` Brendan Higgins
2019-05-22 16:11 ` Dhaval Giani
2019-06-10 11:21 ` Douglas Raillard
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=20190523140356.GN28207@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=alexander.levin@microsoft.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=dan.carpenter@oracle.com \
--cc=dhaval.giani@gmail.com \
--cc=dvyukov@google.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=khilman@baylibre.com \
--cc=knut.omang@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tbird20d@gmail.com \
--cc=willy@infradead.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).