All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Anton Arapov <anton@redhat.com>
Cc: Dave Jones <davej@redhat.com>, "Theodore Ts'o" <tytso@mit.edu>,
	Greg KH <gregkh@linuxfoundation.org>,
	ksummit-2013-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [ATTEND] oops.kernel.org prospect
Date: Tue, 20 Aug 2013 10:22:16 +0200	[thread overview]
Message-ID: <20130820082216.GA13078@pd.tnic> (raw)
In-Reply-To: <20130820080243.GB2613@bandura.laptop>

On Tue, Aug 20, 2013 at 10:02:43AM +0200, Anton Arapov wrote:
> > * Visiting it with chromium gets an annoying warning about the https server
> > ...
> [snip]
> > ...
> > 	Dave
> 
> Thanks, Dave! Will be fixed and improved.

Yeah, collecting oopses is a good idea, so +1.

However, we probably want to think about what exactly we're going to
do with that information. For example, if I want to address an issue,
I probably want to know how I can reproduce the oops - maybe something
like allowing the reporter to add free text note to the oops.

And yes, as tytso already said, we are very often going to need more
info about a system causing the oops (dmesg, lspci, dmidecode, etc,
etc). I'm not sure how we're going to collect that without sacrificing
some privacy. Or maybe, we could be able to ask people to open a bug on
bugzilla.kernel.org where further debugging can take place...

Which reminds me: maybe connecting bug reports on bugzilla.kernel.org
with your stats could also be a way to connect bug reports with
reporters...

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-08-20  8:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130819085405.GA22328@bandura.laptop>
     [not found] ` <20130819145505.GB15178@kroah.com>
     [not found]   ` <20130819151643.GC19070@bandura.laptop>
     [not found]     ` <20130819153939.GA23875@thunk.org>
2013-08-19 15:52       ` [ATTEND] oops.kernel.org prospect Anton Arapov
2013-08-19 21:25         ` Dave Jones
2013-08-20  8:02           ` Anton Arapov
2013-08-20  8:22             ` Borislav Petkov [this message]
2013-08-20 12:37               ` Dave Jones
2013-08-20 13:21                 ` Anton Arapov
2013-08-21 15:13                 ` Borislav Petkov
2013-08-20 15:20           ` [Ksummit-2013-discuss] " Dave Hansen
2013-08-20 15:48             ` Guenter Roeck
2013-08-20 17:02             ` Anton Arapov
2013-08-20 20:58             ` Ben Hutchings
2013-08-20 21:38               ` Anton Arapov
2013-08-20 17:06           ` Anton Arapov
2013-10-04  8:53           ` Anton Arapov
2013-08-21 19:43         ` Francois Romieu
2013-08-22 10:44           ` Anton Arapov
     [not found]         ` <20130821223121.336c71d0@TOMWIJ-GENTOO>
2013-08-22 10:35           ` oops.kernel.org, reporting. [Was: [ATTEND] oops.kernel.org prospect] Anton Arapov
2013-09-06 20:02             ` Joseph Salisbury
2013-09-09  8:49               ` Anton Arapov

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=20130820082216.GA13078@pd.tnic \
    --to=bp@alien8.de \
    --cc=anton@redhat.com \
    --cc=davej@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.