From: Josh Boyer <jdub@us.ibm.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
Linux MTD <linux-mtd@lists.infradead.org>,
"hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si>
Subject: Re: Great jffs2 speedup
Date: Thu, 29 Sep 2005 07:39:09 -0500 [thread overview]
Message-ID: <1127997549.3231.3.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <20050929115243.GB21332@wohnheim.fh-wedel.de>
On Thu, 2005-09-29 at 13:52 +0200, Jörn Engel wrote:
> On Thu, 29 September 2005 13:45:14 +0200, Ferenc Havasi wrote:
> > >
> > Yes, it is true. But if an attacker already has the permission to do it,
> > I think he has many simpler and faster way to crash the system. :)
>
> Doesn't matter. If there is a good way to avoid this, we should do
> it.
>
> Problem is: Maybe there isn't.
Depending on what your definition of DoS is, JFFS2 _without_ EBS or CS
could be considered that already. If mounts take extremely long times
on any decent sized flash, that could be perceived as a DoS.
Think along the lines of "new ogg vorbis player with 4 GiB NAND flash
using JFFS2 as the filesystem". You think people are going to want to
wait for anything over 2 seconds for their music to be available?
I know, I know... far fetched perhaps. But not any more than your
mount/unmount loop :).
josh
next prev parent reply other threads:[~2005-09-29 12:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 9:36 Great jffs2 speedup hinko.kocevar
2005-09-28 10:00 ` Jörn Engel
2005-09-28 15:26 ` hinko.kocevar
2005-09-29 7:53 ` Jörn Engel
2005-09-30 12:26 ` hinko.kocevar
2005-09-29 8:21 ` Ferenc Havasi
2005-09-29 9:34 ` Jörn Engel
2005-09-29 9:44 ` Artem B. Bityutskiy
2005-09-29 9:52 ` Ferenc Havasi
2005-09-29 9:55 ` Jörn Engel
2005-09-29 9:59 ` Artem B. Bityutskiy
2005-09-29 10:12 ` Jörn Engel
2005-09-29 10:21 ` Artem B. Bityutskiy
2005-09-29 10:26 ` Jörn Engel
2005-09-29 11:34 ` Ferenc Havasi
2005-09-29 11:35 ` Jörn Engel
2005-09-29 11:45 ` Ferenc Havasi
2005-09-29 11:52 ` Jörn Engel
2005-09-29 12:39 ` Josh Boyer [this message]
2005-09-29 10:23 ` Ferenc Havasi
2005-09-29 10:29 ` Jörn Engel
2005-09-29 10:45 ` Artem B. Bityutskiy
2005-09-29 11:29 ` Ferenc Havasi
2005-09-29 11:32 ` Artem B. Bityutskiy
2005-09-29 16:10 ` Peter Grayson
2005-09-29 17:45 ` Sergei Sharonov
2005-09-30 4:19 ` Peter Grayson
2005-09-30 8:58 ` Artem B. Bityutskiy
2005-09-30 9:08 ` Artem B. Bityutskiy
2005-09-30 20:25 ` Peter Grayson
2005-10-01 7:01 ` Artem B. Bityutskiy
2005-09-30 21:15 ` Sergei Sharonov
2005-09-30 23:22 ` Peter Grayson
2005-10-01 7:43 ` Artem B. Bityutskiy
2005-09-29 10:15 ` hinko.kocevar
2005-09-29 12:01 ` Ferenc Havasi
2005-09-29 13:07 ` Jörn Engel
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=1127997549.3231.3.camel@windu.rchland.ibm.com \
--to=jdub@us.ibm.com \
--cc=dedekind@yandex.ru \
--cc=hinko.kocevar@cetrtapot.si \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.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