From: Joshua Kwan <joshk@triplehelix.org>
To: Linux-kernel@vger.kernel.org
Subject: Re: slab corruption in test9 (NFS related?)
Date: Sun, 9 Nov 2003 20:23:38 -0800 [thread overview]
Message-ID: <20031110042338.GI956@triplehelix.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0311092007451.3002-100000@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Sun, Nov 09, 2003 at 08:09:40PM -0800, Linus Torvalds wrote:
> In other words, your patch certainly looks obviously correct, but it also
> looks _so_ obviously correct that my alarm bells are going off. If the
> code was quite that broken at counting dentries, how the hell did it ever
> work AT ALL?
From Jargon File (4.3.0, 30 APR 2001) [jargon]:
schroedinbug /shroh'din-buhg/ n. [MIT: from the Schroedinger's Cat
thought-experiment in quantum physics] A design or implementation bug in
a program that doesn't manifest until someone reading source or using
the program in an unusual way notices that it never should have worked,
at which point the program promptly stops working for everybody until
fixed. Though (like {bit rot}) this sounds impossible, it happens; some
programs have harbored latent schroedinbugs for years. Compare
{heisenbug}, {Bohr bug}, {mandelbug}.
Hold on to your horses everyone? :)
--
Joshua Kwan
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-11-10 4:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 23:16 slab corruption in test9 (NFS related?) Burton Windle
2003-11-10 3:04 ` Andrew Morton
2003-11-10 3:05 ` Neil Brown
2003-11-10 4:09 ` Linus Torvalds
2003-11-10 4:23 ` Joshua Kwan [this message]
2003-11-10 4:36 ` Trond Myklebust
2003-11-10 4:42 ` Linus Torvalds
2003-11-10 4:36 ` Neil Brown
2003-11-10 4:45 ` Linus Torvalds
2003-11-10 4:51 ` Andrew Morton
2003-11-10 5:56 ` viro
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=20031110042338.GI956@triplehelix.org \
--to=joshk@triplehelix.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