From: Anton Arapov <anton@redhat.com>
To: kernel@gentoo.org
Cc: linux-kernel@vger.kernel.org
Subject: oops.kernel.org, reporting. [Was: [ATTEND] oops.kernel.org prospect]
Date: Thu, 22 Aug 2013 12:35:16 +0200 [thread overview]
Message-ID: <20130822103516.GA2597@bandura.laptop> (raw)
In-Reply-To: <20130821223121.336c71d0@TOMWIJ-GENTOO>
Hello,
Thank you for contacting me. I will cross-post this to LKML, as there
is an information that might be interested for other folks.
On Wed, Aug 21, 2013 at 10:31:21PM +0200, Tom Wijsman wrote:
> We, the Gentoo Kernel Project Team at Gentoo Linux, might be interested
> to contribute oopses to oops.kernel.org; but from a first look over what
> can be found on the ML and the internet about that site, there seems to
> be no information available about submitting to oops.kernel.org.
This kind of information will be there soon.
> So, could you please highlight the details on how submission happens?
> Does this (have to) happen automatically? Can we do manual submissions?
oops.kernel.org uses the old legacy kerneloops.org's api for data
collecting. Both, http://submit.kerneloops.org/submitoops.php (old) and
http://oops.kernel.org/submitoops.php (new, stick to this one) works today.
Reporting doesn't happen automatically. Two tools available for
sending reports: abrt/libreport (1) and former kerneloops daemon (2).
Either of these can send reports automatically or manually.
(1) https://fedorahosted.org/abrt/ - iirc, is already packaged in gentoo.
(2) There are no link to kerneloops, this is what I was able to google:
http://ftp.debian.org/debian/pool/main/k/kerneloops/kerneloops_0.12+git20090217.orig.tar.gz
Abrt has a better scanner/reporter, which produce less false-positive reports.
I don't know what way Gentoo will choose, but the original kerneloops
daemon requires some love to make it run under systemd and improve the
oops scanner (can be ported from abrt).
The source of _scanner_ abrt/dumpoops_plugin:
https://git.fedorahosted.org/cgit/abrt.git/tree/src/plugins/abrt-dump-oops.c
The source of _reporter_ abrt/libreport/kerneloops_plugin:
https://git.fedorahosted.org/cgit/libreport.git/tree/src/plugins/reporter-kerneloops.c
libreport allows to report manually using CLI:
$ reporter-kerneloops
Usage: reporter-kerneloops [-v] [-c CONFFILE]... -d DIR
> I think that something that "calls home" might become a concern; maybe
> we could still provide that as opt-in, but manual submits would be neat.
Few years of experience with Abrt/Bugzilla reports, people fill the
additional information in less than 2% of all reports. And, the Abrt
team is working towards the least possible interaction with the user.
This is mostly to address privacy concerns, as well as leaving the
possibility to provide additional data.
> Thank you in advance for your explanation.
You are welcome, let me know if you'll need any help further.
Anton.
next prev parent reply other threads:[~2013-08-22 10:35 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
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 ` Anton Arapov [this message]
2013-09-06 20:02 ` oops.kernel.org, reporting. [Was: [ATTEND] oops.kernel.org prospect] 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=20130822103516.GA2597@bandura.laptop \
--to=anton@redhat.com \
--cc=kernel@gentoo.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox