From: Michael Galassi <mgalassi@c-cor•com>
To: Dan Malek <dan@embeddedalley•com>
Cc: ppc embedded list <linuxppc-embedded@ozlabs•org>
Subject: Re: mmap bug (all archs) w/ fix
Date: Tue, 30 Jan 2007 19:33:58 -0800 [thread overview]
Message-ID: <200701310333.l0V3XwBe009802@penguin.ncube.com> (raw)
In-Reply-To: Your message of "Tue, 30 Jan 2007 19:02:32 PST." <9163DAF8-7756-44DA-B6FF-5B9EC1605B00@embeddedalley.com>
>MTD does this very nicely for you, and you don't have
>to write any special programs...... :-)
MTD does have the ability to do this. One might argue about the
philosophical merits of doing in kernel space (hard to debug) what can
trivially be done in user space (trivial to debug). One might also
argue that the mtd code (I've perused it in some detail) takes a rather
cavalier approach to error checking and is thus not optimal for use in
real systems where reliability, dependability, and availability matter.
While our heroic "one" is busy arguing, I'll take a moment and point out
that the Linux kernel harbors a bug, the fix is trivial. As long as the
argument still rages, I'll point out that advice from the "don't fix the
bug, work around it" crowd doesn't carry that much weight with the
paranoid amongst us.
>It's also much safer.
Under what circumstance is buggy kernel code safer than buggy user code?
-michael
next prev parent reply other threads:[~2007-01-31 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 2:54 mmap bug (all archs) w/ fix Michael Galassi
2007-01-31 3:02 ` Dan Malek
2007-01-31 3:33 ` Michael Galassi [this message]
2007-01-31 13:34 ` Gerhard Jaeger
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=200701310333.l0V3XwBe009802@penguin.ncube.com \
--to=mgalassi@c-cor$(echo .)com \
--cc=dan@embeddedalley$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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