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

[Jason Cooper <jason@lakedaemon.net>]

On Sun, May 11, 2014 at 07:18:24PM +0200, Levente Kurusa wrote:
> Hi,
> 
> On Sun, May 11, 2014 at 06:37:47PM +0200, Laurent Pinchart wrote:
> > On Sunday 11 May 2014 18:29:18 Levente Kurusa wrote:
...
> > > Not sure about how would we create the bugzilla entry? I mean, which
> > > section, urgency, etc. how would we decide on those solely based on
> > > the OOPS? Or should we ask the user to fill it out?
> > 
> > Filling a complex form on a handheld device can be pretty tedious. A two steps 
> > procedure that would allow entering long text on a real computer could be an 
> > interesting option.
> > 
> 
> Makes sense.
> 
> What about only asking for an email address and then sending them
> an automated message with a link where they can continue to add more
> information to the report? (i.e. fill out the bugzilla)

Agree.

> I guess we should also be careful with the bugzilla. We really don't
> want propertiary driver crashes added to the bugzilla automatically.

Correct, but the data is still worth recording.

> Nor do we want the same oops added twice, right?

We don't want two bugzilla entries, but we do want to know how many
times this event has happened.

> How would we differentiate between the two - essentially the same -
> oopses?

Hmm, oops cookie?  hex string of 32/64 bits read off of the entropy
pool?  This would give us an accurate number of events even if a user
scans multiple times.

thx,

Jason.