From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008
Date: Fri, 23 May 2008 09:42:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805230927200.3081@woody.linux-foundation.org> (raw)
In-Reply-To: <4836EE8C.1010200@linux.intel.com>
On Fri, 23 May 2008, Arjan van de Ven wrote:
>
> Per file statistics
> [I'd love to borrow Linus' gitstat stuff for this to get a nicer presentation
> of the per file/directory data]
The algorithm is very simple. Just sort your filenames alphabetically, and
then you can do it with a simple 40-line recursive function and a trivial
data structure. See the git sources, diff.c: gather_dirstat().
Or just do "git show 7df7c019c2a46672c12a11a45600cdc698e03029" in git to
show the commit that introduces --dirstat.
(In fact, much of the dirstat code is the thing that turns it into
percentages, so it has some setup code that first calculates the total
number of changes, and the printout code spends effort in generating the
percentage (well, permille) and not showing insignificant stuff - whether
you'd want/need that for this is debatable)
> Rank 1: __register_sysctl_paths
> Reported 1260 times (2491 total reports)
> [tainted] Duplicate /proc registration. Bug in the madwifi driver
> (Occasionally seen in the parport driver)
> This oops was last seen in version 2.6.25.4, and first seen in 2.6.25-rc3.
> More info:
> http://www.kerneloops.org/searchweek.php?search=__register_sysctl_paths
Btw, can you try to call these warnings, not oopses? It's not an oops, and
it's not even reported as an oops in the overviews on the top-level things
on the web-site, so your scripts do know it's not an oops - but then in
this summary and in the "detailed information" reports it's called an oops
again.
It's a WARN_ON, and yeah, while they can be bad, it's still different
from an actual oops.
Linus
next prev parent reply other threads:[~2008-05-23 16:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 16:19 Arjan van de Ven
2008-05-23 16:23 ` Top 10 bugs/warnings for the week of May " Arjan van de Ven
2008-05-23 16:42 ` Linus Torvalds [this message]
2008-05-23 17:35 ` Top 10 bugs/warnings for the week of March " Arjan van de Ven
2008-05-23 19:31 ` Alan Cox
2008-05-24 0:15 ` Chris Wright
2008-05-24 5:07 ` Arjan van de Ven
2008-05-26 9:36 ` Ingo Molnar
2008-05-24 5:32 ` Greg KH
2008-05-24 22:23 ` Jan Kara
2008-05-24 22:30 ` Arjan van de Ven
2008-05-24 22:45 ` Theodore Tso
2008-05-25 11:58 ` Stefan Richter
2008-05-26 9:39 ` Ingo Molnar
2008-05-26 10:16 ` Theodore Tso
2008-05-26 10:48 ` Ingo Molnar
2008-05-26 16:20 ` Jan Kara
2008-05-26 16:48 ` Ingo Molnar
2008-05-26 17:01 ` Theodore Tso
2008-05-26 17:09 ` Oliver Neukum
2008-05-26 17:28 ` Bart Van Assche
2008-05-26 17:38 ` Jan Kara
2008-05-26 17:50 ` Theodore Tso
2008-05-26 18:23 ` Ingo Molnar
2008-05-27 6:12 ` Oliver Neukum
2008-05-27 11:41 ` Pavel Machek
2008-05-27 3:49 ` Greg KH
2008-05-27 11:40 ` Pavel Machek
2008-05-26 14:52 ` Stefan Richter
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=alpine.LFD.1.10.0805230927200.3081@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®