From: Arjan van de Ven <arjan@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Mark Fasheh <mark.fasheh@oracle.com>,
kurt.hackel@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] OCFS2: __init / __exit problem
Date: Sat, 07 Jan 2006 22:51:17 +0100 [thread overview]
Message-ID: <1136670678.2936.46.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060107214947.GW3774@stusta.de>
>
> This is the common problem that such error paths are only used once
> every dozen years and therefore get no real testing coverage...
Rusty presented some brilliant tool for this at OLS this year... I bet
that could be used for filesystems as well (Rusty uses it for netfilter
testing)
next prev parent reply other threads:[~2006-01-07 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:20 Jan-Benedict Glaw
2006-01-07 19:07 ` [2.6 patch] " Adrian Bunk
2006-01-07 21:38 ` Mark Fasheh
2006-01-07 21:49 ` Adrian Bunk
2006-01-07 21:51 ` Arjan van de Ven [this message]
2006-01-08 0:23 ` Randy.Dunlap
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=1136670678.2936.46.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
/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®