public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ferenc Havasi <havasi@inf.u-szeged.hu>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
	"hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si>,
	Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Great jffs2 speedup
Date: Thu, 29 Sep 2005 13:34:44 +0200	[thread overview]
Message-ID: <433BD154.1050403@inf.u-szeged.hu> (raw)
In-Reply-To: <20050929102620.GE18741@wohnheim.fh-wedel.de>

Jörn Engel wrote:

>On Thu, 29 September 2005 14:21:21 +0400, Artem B. Bityutskiy wrote:
>  
>
>>Jörn Engel wrote:
>>    
>>
>>>Dummy argument.  Wear levelling is just a means to avoid the real
>>>problem - early wear-out of specific blocks.  Spending one erase block
>>>for cs is pretty sane, as long as this block doesn't wear-out well
>>>before the rest.
>>>      
>>>
>>"As long as" is the essential part. If it is true - nice. In general 
>>this can't be true. And, anticipating your remark, I agree that it still 
>>may have its place. :-)
>>    
>>
>
>Agreed.  In general, this patch opens an option for a DoS attack.
>  
>
Maybe I don't understand something. How makes CS possible DoS attacks?

Ferenc

  reply	other threads:[~2005-09-29 11:31 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 [this message]
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
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=433BD154.1050403@inf.u-szeged.hu \
    --to=havasi@inf.u-szeged.hu \
    --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