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;
MIME-Version: 1.0
In-Reply-To: <CACT4Y+aiSXsyFqXueRGXeVeY6KAJ4M2Oy6RZWFnNS_d9Z9pAnw@mail.gmail.com>
References: <CAPhKKr_XFzGcBBuQ51w7HjZd_Kq3nTOB6uAFG2vP5JH+Vx_eng@mail.gmail.com>
 <CACT4Y+Y+6arxj4=72DZSj45u5kjKRksJZ7c6pBLeFDxUSBFwOg@mail.gmail.com>
 <20181008142300.3aacaabe@gandalf.local.home> <CAPhKKr8QvK3bkT6gQB9jc31Cx+gLmZwRnKuRUD_1xaidwL14Dg@mail.gmail.com>
 <CACT4Y+aiSXsyFqXueRGXeVeY6KAJ4M2Oy6RZWFnNS_d9Z9pAnw@mail.gmail.com>
From:   Dmitry Vyukov <dvyukov@google.com>
Date:   Thu, 11 Oct 2018 11:41:47 +0200
Message-ID: <CACT4Y+a6stTxMritOizwvcbkQAJoGF3MbBmBFu-8x3o13Vxc5g@mail.gmail.com>
Subject: Re: [Announce] LPC 2018: Testing and Fuzzing Microconference
To:     Dhaval Giani <dhaval.giani@gmail.com>,
        Paul McKenney <paulmck@linux.vnet.ibm.com>
Cc:     Steven Rostedt <rostedt@goodmis.org>,
        Sasha Levin <alexander.levin@microsoft.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Alice Ferrazzi <alice.ferrazzi@gmail.com>,
        Kevin Hilman <khilman@baylibre.com>,
        Tim Bird <tbird20d@gmail.com>,
        Laura Abbott <labbott@redhat.com>,
        gustavo.padovan@collabora.co.uk,
        "Carpenter,Dan" <dan.carpenter@oracle.com>,
        Matthew Wilcox <willy@infradead.org>, knut.omang@oracle.com,
        Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Oct 11, 2018 at 10:54 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
>>> On Mon, 8 Oct 2018 19:02:51 +0200
>>> Dmitry Vyukov <dvyukov@google.com> wrote:
>>>
>>> > On Wed, Sep 19, 2018 at 7:13 PM, Dhaval Giani <dhaval.giani@gmail.com> wrote:
>>> > > Hi folks,
>>> > >
>>> > > Sasha and I are pleased to announce the Testing and Fuzzing track at
>>> > > LPC [ 1 ]. We are planning to continue the discussions from last
>>> > > year's microconference [2]. Many discussions from the Automated
>>> > > Testing Summit [3] will also continue, and a final agenda will come up
>>> > > only soon after that.
>>> > >
>>> > > Suggested Topics
>>> > >
>>> > > - Syzbot/syzkaller
>>> > > - ATS
>>> > > - Distro/stable testing
>>> > > - kernelci
>>> > > - kernelci auto bisection
>>> > > - Unit testing framework
>>> > >
>>> > > We look forward to other interesting topics for this microconference
>>> > > as a reply to this email.
>>> >
>>> > Hi Dhaval and Sasha,
>>> >
>>> > My syzbot talk wasn't accepted to main track, so I would like to do
>>> > more or less full-fledged talk on the microconf. Is it possible?
>>>
>>> Hi Dmitry,
>>>
>>> Note, microconfs are not for full-fledged talks. They are to be
>>> discussion focused. You can have a 5-10 minute presentation that leads
>>> up to discussion of future work, but we like to refrain from any talks
>>> about what was done if there's nothing to go forward with.
>>
>> Dmitiry,
>>
>> Can you clarify the scope of what you want to discuss during the
>> microconference? Further to what Steven said, we don't want
>> presentations (So 3, maybe 4 slides). We want discussions about future
>> work.
>>
>> Thanks!
>> Dhaval
>
>
> Hi Steven, Dhaval,
>
> Acknowledged.
>
> Then smaller topic that would benefit from discussion are:
>
> the main one being:
>
> 1. syzbot: developer process; unfixed bugs; bug triage; what's
> working? what's not? why? how can we make more parts work? collecting
> feedback

+Paul as Plumbers committee representative
And +Greg is already here as Kernel Summit representative

Re syzbot talk (around process and feedback).
I've submitted this as proposal to Plumbers, it did not make it to
main track but it's in backlog (I am a reserve speaker).
Sergey suggested to submit this as proposal for Kernel Summit TECH
TOPIC. It would probably benefit from more kernel maintainers in the
room.

Now I am somewhat troubled, if I submit the talk for Kernel Summit and
then suddenly I materialize as speaker on Plumbers too. It's not a
good idea to do the same talk twice, right?
The questions are:
1. Is it a good fit for Kernel Summit TECH TOPIC?
2. What should I do if I suddenly accepted to both Summit and
Plumbers? I probably could prepare a second, different talk for
Plumbers then (it wasn't announced yet).
3. If the talk is accepted to Summit, what should we do with Testing
MC part? Withdraw?


> 2. how to increase test coverage/find more bugs, in particular:
>  - adding manual spot KASAN/KMSAN checks into kernel codebase
>  - stubbing hardware/external inputs to kernel for testing
>  - description of kernel interfaces (again)
>
> 3. dealing with kernel console output mess
>  - intermixed/split lines
>  - understand when/how kernel crashed
>  - and where is that message
>  - crash identity