From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] don't divide by 0 when trying to mount ext3
Date: Mon, 8 Nov 2004 23:10:25 +0100 [thread overview]
Message-ID: <20041108221025.GA19823@bitwizard.nl> (raw)
In-Reply-To: <20041108215402.GB2946@pclin040.win.tue.nl>
On Mon, Nov 08, 2004 at 10:54:02PM +0100, Andries Brouwer wrote:
> On Mon, Nov 08, 2004 at 10:27:11PM +0100, Rogier Wolff wrote:
>
> > There are now three cases that end up with the same message and
> > same error from userspace viewpoint. There are many cases where
> > debugging a problem is helped when it's possible to find out exactly
> > which test determined that the filesystem could not be mounted.
>
> Strings are expensive. Don't like to add worthless code.
> We lived without this for years, so it is not a frequent occurrence.
> If you have a bad ext2/ext3 system, e2fsck will find what is wrong.
int cpos=0;
if (++cpos && (errorposibility1 ) ) goto error_handling;
[...]
if (++cpos && (errorposibility2 ) ) goto error_handling;
[...]
if (++cpos && (errorposibility3 ) ) goto error_handling;
[...]
error_handling:
printk (".... %d ...", cpos);
Rogier.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
prev parent reply other threads:[~2004-11-08 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 19:59 [PATCH] don't divide by 0 when trying to mount ext3 Andries Brouwer
2004-11-08 21:27 ` Rogier Wolff
2004-11-08 21:54 ` Andries Brouwer
2004-11-08 22:10 ` Rogier Wolff [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=20041108221025.GA19823@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=aebr@win.tue.nl \
--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 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.