From: Arjan van de Ven <arjan@linux.intel.com>
To: Theodore Tso <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
protasnb@gmail.com
Subject: Re: Top kernel oopses/warnings this week
Date: Mon, 17 Dec 2007 22:58:54 -0800 [thread overview]
Message-ID: <47676FAE.30200@linux.intel.com> (raw)
In-Reply-To: <20071218023141.GM7070@thunk.org>
Theodore Tso wrote:
> On Mon, Dec 17, 2007 at 04:21:12PM -0800, Linus Torvalds wrote:
>> which also gets bonus points for being totally unreadable, and thus 100%
>> in the spirit of uuid's.
>
> Heh. UUID's don't have to be readable; just universally unique. Code
> on the other hand should be readable. :-)
Linus' suggested... improvement should either be done in all 3 places or none ;)
Since you're the maintainer... what's your suggestion?
>
> If you want something more readable, you could print the MAC address
> and boot time. Of course some crazy people seem to think leaking the
> MAC address will somehow be a privacy violation. And printing a
> random UUID is a lot simpler....
boot UUID is nice in that it's different each boot, so that an oops that happens twice will have a
different UUID even if it's the same machine, while repeat-reports of the same oops will have
the same UUID. So I very much like to use some form of UUID; since the boot UUID has the
same properties I was happy to share this; if it gets too ugly or evil code wise I can always
pick something else ;-)
next prev parent reply other threads:[~2007-12-18 7:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 18:46 Top kernel oopses/warnings this week Arjan van de Ven
2007-12-14 18:58 ` Dave Jones
2007-12-14 21:57 ` Andrew Morton
2007-12-14 22:25 ` Natalie Protasevich
2007-12-15 0:38 ` Arjan van de Ven
2007-12-14 22:12 ` Jon Masters
2007-12-15 15:49 ` Stefan Richter
2007-12-15 18:21 ` Arjan van de Ven
2007-12-15 19:44 ` Stefan Richter
2007-12-17 18:25 ` Zach Brown
2007-12-17 18:41 ` Arjan van de Ven
2007-12-17 2:51 ` Dave Jones
2007-12-17 12:33 ` Jon Masters
2007-12-17 13:13 ` Stefan Richter
2007-12-17 16:40 ` Arjan van de Ven
2007-12-17 17:23 ` Ingo Molnar
2007-12-17 21:36 ` Arjan van de Ven
2007-12-17 21:58 ` Theodore Tso
2007-12-17 22:58 ` Tony Luck
2007-12-17 23:17 ` Arjan van de Ven
2007-12-17 23:26 ` Tony Luck
2007-12-17 23:47 ` Arjan van de Ven
2007-12-18 0:21 ` Linus Torvalds
2007-12-18 0:39 ` Arjan van de Ven
2007-12-18 2:31 ` Theodore Tso
2007-12-18 6:58 ` Arjan van de Ven [this message]
2007-12-18 17:53 ` Matt Mackall
2007-12-18 18:28 ` Theodore Tso
2007-12-18 18:45 ` Linus Torvalds
2007-12-18 10:11 ` Jon Masters
2007-12-18 18:06 ` Arjan van de Ven
2007-12-18 18:13 ` Matt Mackall
2007-12-18 18:19 ` Arjan van de Ven
2007-12-18 17:48 ` Matt Mackall
2007-12-18 23:37 ` Arjan van de Ven
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=47676FAE.30200@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=protasnb@gmail.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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.