Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel

[Jason Cooper <jason@lakedaemon.net>]

On Mon, May 12, 2014 at 03:48:32PM +0200, Lukáš Czerner wrote:
> On Mon, 12 May 2014, David Woodhouse wrote:
> 
> > Date: Mon, 12 May 2014 10:23:05 +0100
> > From: David Woodhouse <dwmw2@infradead.org>
> > To: Josh Triplett <josh@joshtriplett.org>
> > Cc: PJ Waskiewicz <pjwaskiewicz@gmail.com>,
> >     Jason Cooper <jason@lakedaemon.net>,
> >     ksummit-discuss@lists.linuxfoundation.org,
> >     Anton Arapov <arapov@gmail.com>, Sarah A Sharp <sarah@minilop.net>,
> >     Dirk Hohndel <hohndel@infradead.org>
> > Subject: Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel
> > 
> > On Sun, 2014-05-11 at 23:13 -0700, Josh Triplett wrote:
> > > On Sun, May 11, 2014 at 07:38:14PM -0700, H. Peter Anvin wrote:
> > > > As valuable as I obviously believe this project is, is there actually
> > > > anything that warrants discussion at the Kernel Summit?  It seems like
> > > > something to Just Do[TM].
> > > 
> > > I believe there is actually a key part of this discussion to have at
> > > Kernel Summit.  We don't need to discuss the technical details of the
> > > implementation; we do need to discuss the implications of enabling mass
> > > oops-reporting, the infrastructure and information we want to include in
> > > codes valid for the next decade or so, the tradeoffs between ease of
> > > reporting and value of the reports, some potential approaches to
> > > aggregate the date, and similar.
> > 
> > In particular, can we avoid the silly trap of the ---[cut here]--- which
> > comes between a kernel oops, and the potentially useful messages that
> > were printed right before it.
> 
> Also how to communicate that we usually need the first oops ?

Well, the QR code can only hold one oops anyway.  Printing the code for
the first should be pretty simple to implement.

thx,

Jason.