From: Oleg Drokin <green@linuxhacker.ru>
To: "Max A. Krasilnikov" <pseudo@colocall.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs one user DoS?
Date: Mon, 6 Oct 2003 22:29:00 +0300 [thread overview]
Message-ID: <20031006192900.GA18447@linuxhacker.ru> (raw)
In-Reply-To: <20031004120625.GA41175@colocall.net>
Hello!
On Sat, Oct 04, 2003 at 03:06:25PM +0300, Max A. Krasilnikov wrote:
> I have found such strange thing:
> pseudo@avalon at 14:04:00 ~> dd if=/dev/zero of=file bs=1 count=0 seek=1000000000000
> After that my Intel Celeron 800 MHz/384M RAM 60G/Seagate U6 under
> Linux-2.4.22-grsec on reiserfs was utilized 100% for more than 2 hours.
> dd process can't be killed.
> Is this my flow or real bug?
This particular problem is fixed in current 2.4 bk tree (and the fix
will be in 2.4.23). Also this problem does not exist in 2.6 for some time now.
Bye,
Oleg
prev parent reply other threads:[~2003-10-06 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 12:06 reiserfs one user DoS? Max A. Krasilnikov
2003-10-04 16:08 ` Hans Reiser
2003-10-05 16:09 ` Christian Kujau
2003-10-05 23:51 ` Erik Tews
2003-10-06 2:03 ` Mike Fedyk
2003-10-06 2:14 ` viro
2003-10-06 19:29 ` Oleg Drokin [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=20031006192900.GA18447@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pseudo@colocall.net \
/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