From: Ingo Oeser <ioe-lkml@axxeo.de>
To: Matthew Wilcox <willy@parisc-linux.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, matthew@wil.cx
Subject: Re: [PATCH] Releasing resources with children
Date: Mon, 14 Mar 2005 22:49:10 +0100 [thread overview]
Message-ID: <200503142249.11107.ioe-lkml@axxeo.de> (raw)
In-Reply-To: <20050314181108.A4705@flint.arm.linux.org.uk>
Russell King wrote:
> The only thing I'd question is whether we really need to BUG_ON() here.
> ISTR Linus' policy for BUG()/BUG_ON() was only if the condition lead
> directly to a filesystem-corrupting bug.
I consider it quite effective to flag interface violations.
Programming by contract anyone? ;-)
Regards
Ingo Oeser
prev parent reply other threads:[~2005-03-14 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 17:49 Matthew Wilcox
2005-03-14 18:11 ` Russell King
2005-03-14 21:49 ` Ingo Oeser [this message]
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=200503142249.11107.ioe-lkml@axxeo.de \
--to=ioe-lkml@axxeo.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=willy@parisc-linux.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®