All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Dhaval Giani <dhaval.giani@gmail.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
Subject: Re: [Announce] LPC 2018: Testing and Fuzzing Microconference
Date: Thu, 11 Oct 2018 10:54:20 +0200	[thread overview]
Message-ID: <CACT4Y+aiSXsyFqXueRGXeVeY6KAJ4M2Oy6RZWFnNS_d9Z9pAnw@mail.gmail.com> (raw)
In-Reply-To: <CAPhKKr8QvK3bkT6gQB9jc31Cx+gLmZwRnKuRUD_1xaidwL14Dg@mail.gmail.com>

On Wed, Oct 10, 2018 at 5:47 PM, Dhaval Giani <dhaval.giani@gmail.com> wrote:
> On Mon, Oct 8, 2018 at 11:23 AM Steven Rostedt <rostedt@goodmis.org> 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

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

  reply	other threads:[~2018-10-11  8:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPhKKr_XFzGcBBuQ51w7HjZd_Kq3nTOB6uAFG2vP5JH+Vx_eng@mail.gmail.com>
2018-09-22 12:52 ` [Announce] LPC 2018: Testing and Fuzzing Microconference Matthew Wilcox
2018-09-24 13:42   ` Dmitry Vyukov
2018-09-24 15:56     ` Knut Omang
2018-10-08 17:02 ` Dmitry Vyukov
2018-10-08 18:23   ` Steven Rostedt
2018-10-10 15:47     ` Dhaval Giani
2018-10-11  8:54       ` Dmitry Vyukov [this message]
2018-10-11  9:41         ` Dmitry Vyukov
2018-10-11 13:40           ` Steven Rostedt
2018-11-05 18:05 ` Gustavo Padovan
2018-11-08 16:30   ` Dhaval Giani
2018-11-08 18:12     ` Kevin Hilman
2018-09-19 17:14 Dhaval Giani
2018-10-02 20:22 ` Liam R. Howlett
2018-10-02 21:03   ` Sasha Levin
2018-10-03 18:21     ` Dhaval Giani
2018-10-03 19:16     ` Liam R. Howlett
2018-10-03 22:01       ` Sasha Levin
2018-10-16 19:46 ` Dan Carpenter
2018-10-30 22:05 ` Knut Omang

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=CACT4Y+aiSXsyFqXueRGXeVeY6KAJ4M2Oy6RZWFnNS_d9Z9pAnw@mail.gmail.com \
    --to=dvyukov@google.com \
    --cc=alexander.levin@microsoft.com \
    --cc=alice.ferrazzi@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dhaval.giani@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=khilman@baylibre.com \
    --cc=knut.omang@oracle.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.