The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Anton Arapov <anton@redhat.com>
To: Dave Hansen <dave@sr71.net>
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: [Ksummit-2013-discuss] [ATTEND] oops.kernel.org prospect
Date: Tue, 20 Aug 2013 19:02:15 +0200	[thread overview]
Message-ID: <20130820170215.GA6750@bandura.laptop> (raw)
In-Reply-To: <52138924.1040905@sr71.net>

On Tue, Aug 20, 2013 at 08:20:04AM -0700, Dave Hansen wrote:
> On 08/19/2013 02:25 PM, Dave Jones wrote:
> > * This bug last seen: 2013-08-17
> >   Also useful here would be something like:
> >   Seen on: 3.2-rc2, 3.10-rc10  (You can probably just list earliest/latest rather than
> >    every single kernel it's been seen on, unless you want a 'show all' button)
> 
> Once you have the "seen on" stuff sorted out, it would also be really
> nice to be able to easily select bugs only seen on "versions after 3.8",
> just so we can filter out some of the older stuff.  The kernel version
> in the filter is useful, but would be much more so if we had ranges,
> even if it was just "newer than $foo".
This is good idea.


> When you go to "Show Raw Oops", it usually doesn't show up for me in
> Chrome.  There's a javascript error:
> > The page at https://oops.kernel.org/browse-reports/oops-detail/?id=30565# displayed insecure content from http://oops.kernel.org/get-raw.php?id=30565&token=a94733d146ae15f8cec871d4f238956da80d7c5322f6253f9b49d4c5cc8fe8a1.
> If I go over and load the page as plain old http, it works fine.  Also,
> when those oopses show up, the font is variable-width.  It would
> probably be a wee bit easier to read if it were displayed in a
> fixed-width font.
The latest version of Firefox should have the same issue, it is
prohibited now to show/get insecure content under the secure
connection. I will most probably redirect any https request to http
automatically to avoid this issue.


> 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.

Will put into todo list, might be someday...

> Anyway... cool stuff.  I always forget that oops.kernel.org is there,
> but it's always fun to poke around when I run across it. :)

Thanks,
Anton.

>requests accumulated:
http://trello.com/b/ZvLKCkJX/oops-kernel-org-support-and-development

  parent reply	other threads:[~2013-08-20 17:03 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 [this message]
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=20130820170215.GA6750@bandura.laptop \
    --to=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