From: Mike Fedyk <mfedyk@matchmail.com>
To: Erik Tews <erik@debian.franken.de>
Cc: Christian Kujau <evil@g-house.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs one user DoS?
Date: Sun, 5 Oct 2003 19:03:42 -0700 [thread overview]
Message-ID: <20031006020342.GH1205@matchmail.com> (raw)
In-Reply-To: <20031005235149.GA3993@debian.franken.de>
On Mon, Oct 06, 2003 at 01:51:49AM +0200, Erik Tews wrote:
> On Sun, Oct 05, 2003 at 06:09:24PM +0200, Christian Kujau wrote:
> > Hans Reiser schrieb:
> > >>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?
> > >>
> > >it is fixed in reiser4. linux has a lot of DOS vulerabilities to logged
> > >in users, mostly due to the ability to consume all of some resource or
> > >another. forgive me for not discussing them publicly.;-)
> >
> > perhaps "ulimit" could help here.
>
> Really? If I got a process which is unkillable, how can the kernel kill
> this process if it runs out of cpu-time?
If it is unkillable, you're either talking about kernel bugs or NFS, and
root should be able to kill a user process that has run out of ulimit
resources.
next prev parent reply other threads:[~2003-10-06 2:03 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 [this message]
2003-10-06 2:14 ` viro
2003-10-06 19:29 ` Oleg Drokin
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=20031006020342.GH1205@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=erik@debian.franken.de \
--cc=evil@g-house.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.