From: Ben Hutchings <ben@decadent.org.uk>
To: Dave Hansen <dave@sr71.net>
Cc: Dave Jones <davej@redhat.com>, Anton Arapov <anton@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: [Ksummit-2013-discuss] [ATTEND] oops.kernel.org prospect
Date: Tue, 20 Aug 2013 21:58:12 +0100 [thread overview]
Message-ID: <20130820205812.GZ7729@decadent.org.uk> (raw)
In-Reply-To: <52138924.1040905@sr71.net>
On Tue, Aug 20, 2013 at 08:20:04AM -0700, Dave Hansen wrote:
[...]
> This is a much more minor nit, but the source code links (like clicking
> on bad_page from here:
> https://oops.kernel.org/browse-reports/oops-detail/?id=30565#) from the
> traces for the distribution kernels link over to mainline kernel source.
> This means that the line numbers don't _quite_ line up. It would be
> really cool if it was able to dump you right over to a copy of the
> Debian-specific source in that bug's case. But, this is a generic
> problem that folks have who work across lots of distros: you don't
> always have the right source in front of you for any given kernel.
[...]
For Debian kernels this should be quite easy. The sources are
browseable at:
http://sources.debian.net/src/linux/$PACKAGE_VERSION/$FILE#L$LINE
The package version is not the same as the kernel release string,
but appears at the end of the same line in oops messages, e.g. for
<http://oops.kernel.org/browse-reports/oops-detail/?id=30218> the
package version is 3.10.1-1.
This doesn't work for versions older than 3.2, or those with the RT
patchset, as sources.debian.net can't show the patched source for
these.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
next prev parent reply other threads:[~2013-08-20 20:58 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 ` 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 [this message]
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=20130820205812.GZ7729@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=anton@redhat.com \
--cc=dave@sr71.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome