From: "Brian J. Fox" <bfox@ua.com>
To: dwmw2@infradead.org
Cc: rob@sysgo.de, linux-mtd@lists.infradead.org, joern@wohnheim.fh-wedel.de
Subject: Re: MTD concat layer
Date: Mon, 18 Feb 2002 07:53:29 -0800 [thread overview]
Message-ID: <E16cq6b-0004Hq-00@speedy.datawave.net> (raw)
In-Reply-To: <16804.1014023155@redhat.com> (message from David Woodhouse on Mon, 18 Feb 2002 09:05:55 +0000)
From: David Woodhouse <dwmw2@infradead.org>
Cc: "Brian J. Fox" <bfox@ua.com>, linux-mtd@lists.infradead.org,
J?rn Engel <joern@wohnheim.fh-wedel.de>
Date: Mon, 18 Feb 2002 09:05:55 +0000
Sender: David Woodhouse <dwmw2@redhat.com>
There is never any excuse for passing invalid offset/length to the
erase function - even the ioctl code can do a sanity check before
passing through the values provided by the user.
That's right.
For errors which can understandably occur, your concerns are valid
and we should ensure sanity by failing the request as safely as
possible, doing nothing else.
This is not such an error. As long as the ioctl() has an
appropriate sanity check, the occurrence of such an error indicates
that the kernel code is completely broken. Better to BUG()
BUG() is completely acceptable. It allows the driver to be fixed.
It's also orthogonal to the original question. Erasing blocks is
simply a way to guarantee that data has been irrevocably lost.
Brian
== The Difference Between Cultures: ==
Einigkeit und Recht und Freiheit
Liberte', E'galite', Fraternite'
Sex, drugs and rock'n'roll
next prev parent reply other threads:[~2002-02-18 15:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 18:40 MTD concat layer Robert Kaiser
2002-02-13 7:56 ` Suspend Erase bug in cfi_cmdset0001.c Joakim Tjernlund
2002-02-14 8:17 ` Joakim Tjernlund
2002-02-13 11:00 ` MTD concat layer Joakim Tjernlund
2002-02-13 11:04 ` David Woodhouse
2002-02-13 11:34 ` Robert Kaiser
2002-02-13 11:37 ` Robert Schwebel
2002-02-13 13:33 ` Daniel Engström
2002-02-13 14:01 ` Eric W. Biederman
2002-02-15 15:58 ` David Woodhouse
2002-02-15 17:43 ` Robert Kaiser
2002-02-15 18:02 ` David Woodhouse
2002-02-15 18:40 ` Jörn Engel
2002-02-16 10:33 ` Robert Kaiser
2002-02-16 10:43 ` Robert Kaiser
2002-02-16 10:43 ` David Woodhouse
2002-02-16 11:03 ` Robert Kaiser
2002-02-16 11:08 ` David Woodhouse
2002-02-16 14:56 ` Brian J. Fox
2002-02-17 10:36 ` Robert Kaiser
2002-02-17 19:05 ` Brian J. Fox
2002-02-18 8:48 ` Robert Kaiser
2002-02-18 9:05 ` David Woodhouse
2002-02-18 15:53 ` Brian J. Fox [this message]
2002-02-18 17:01 ` Robert Kaiser
2002-02-18 17:02 ` David Woodhouse
2002-02-18 15:46 ` Brian J. Fox
2002-02-20 14:28 ` Jonas Holmberg
2002-02-20 15:35 ` Robert Kaiser
2002-02-21 14:51 ` Jonas Holmberg
2002-02-26 11:32 ` Robert Kaiser
2002-03-06 13:37 ` Jonas Holmberg
2002-03-06 16:02 ` Robert Kaiser
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 11:14 Jonas Holmberg
2002-03-08 16:08 Robert Kaiser
2002-03-08 16:22 ` David Woodhouse
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=E16cq6b-0004Hq-00@speedy.datawave.net \
--to=bfox@ua.com \
--cc=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rob@sysgo.de \
/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