Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3411685yba; Tue, 23 Apr 2019 03:24:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqzJRnilOvgMH555ksMXZ2zaXt91w8hdr7f+haAt+jROhHvdy9ca/ompqxxai52oKiGoKACU X-Received: by 2002:a62:4602:: with SMTP id t2mr25923063pfa.26.1556015082116; Tue, 23 Apr 2019 03:24:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556015082; cv=none; d=google.com; s=arc-20160816; b=bqses28A/2sv8SnLDC76tAWUId+VbjoPrZd5b4/U5gCFrg9K70pBm4EPCZT4ajHNzP W1c9h9J8gbXVUZxM8/dYnew/P6GRZlV7Qzl7s2lXZXkuL2mmoRNRk5cjwmC+Dg6WFjxd r6ncaDH8Alaj26rUF4iQsjauVqj6LE4T6EYz/Z2MCAj4tGEUKixh6YAXEfqYw5RXxdKE HzmbOpe4VHEvsqhUjoyyDv25LwaW2RpzQo1Kl+NWFjlT5OQ1DhnsxWwJJiIMhe/VEmqS Buu5oG8ESw42GMXs6LdydKg4FZQgoF/AkiljYRfiFzR9P586KPM5y0y5TLY+YcNTQ7DV b3JA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=+MYMF7DPNiqNFmNgq4k5xEVHlMAbW++IB2Gvj25zZWA=; b=Gpat4aslAlS/+b73xNoxpbpaIstl99JaqX4HnJOA+yV8sig4kCw45hsaWLeAywXd2K rI3sGLNkwS9Bekv9nCHnHWYZNToEjs0E7b3QHIxqTFcvwF6m4qvx0oFeVLwDjqsrszCW nuxEiN6HT4AhMlHD7NXfptzR0uXTYSqrFoIYsP8a4RVStOxHpV0PSwp29u8lzPc+QnAM 2LTZaUPU05+g3a8eyDEg3PfWYucWKR20MAgdy1QiEgfUHJbEuquFDSOrk/0i7QJC6ysQ 8xEQfevnn/LKK7t2RR6mIBA+gQilLBHjMLa1ZtO8hgEnCsJBPwGnjTmABcnw3LWqB/Eh +nrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v1si16509319pfv.192.2019.04.23.03.24.26; Tue, 23 Apr 2019 03:24:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727305AbfDWKW6 (ORCPT + 99 others); Tue, 23 Apr 2019 06:22:58 -0400 Received: from foss.arm.com ([217.140.101.70]:53430 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726150AbfDWKW6 (ORCPT ); Tue, 23 Apr 2019 06:22:58 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A5129374; Tue, 23 Apr 2019 03:22:57 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6D5643F557; Tue, 23 Apr 2019 03:22:55 -0700 (PDT) Date: Tue, 23 Apr 2019 11:22:50 +0100 From: Mark Rutland To: Dhaval Giani Cc: Sasha Levin , shuah , Kevin Hilman , Tim Bird , LKML , Steven Rostedt , "Carpenter,Dan" , willy@infradead.org, gustavo.padovan@collabora.co.uk, Dmitry Vyukov , knut.omang@oracle.com, Nick Desaulniers Subject: Re: Linux Testing Microconference at LPC Message-ID: <20190423102250.GA56999@lakrids.cambridge.arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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). Thanks, Mark.