From: Kasper Dupont <kasperd@daimi.au.dk>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] ext2 and ext3 block reservations can be bypassed
Date: Tue, 14 May 2002 20:25:08 +0200 [thread overview]
Message-ID: <3CE15684.989AB0D3@daimi.au.dk> (raw)
In-Reply-To: <200205131709.g4DH9Fjv006328@pincoya.inf.utfsm.cl> <3CE1300A.990919E2@daimi.au.dk> <20020514115655.A22935@mark.mielke.cc>
Mark Mielke wrote:
>
> 1) You can always submit a patch, and see whether other people approve of it.
I might decide to do that. But I wouldn't spend the time
without first knowing if:
a) There were some very good reasons not to change it.
b) Somebody knowing this code by heart could write a
patch in five minutes.
>
> 2) If you won't do it, why would somebody else working on something that
> provides lower latency to user process response time, or improvement
> to the IDE drivers, take the time to deal with this issue?
I don't intend to try to force somebody to do it, if
they have more important things to do.
>
> As it is, there are plenty of other denial-of-service type attacks
> that can be performed that would be more effective than the 'exploit'
> you have mentioned. Your proposal would need to be 'fix them all', if
> your complaint is that Linux has a security hole.
It surely would be nice to prevent all DoS attacks. But
of course that would require a lot of work. However I
think most other DoS attacks could be solved by a reboot.
>
> If you complaint is that an administrator might mistakenly believe
> that it is a security feature, I suggest your understand that this is
> merely one issue of quite a few. If the administrator is not aware of
> issues such as these, perhaps they should not be an administrator?
We cannot blame administrators before the documentation
has been changed.
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razor-report@daimi.au.dk
next prev parent reply other threads:[~2002-05-14 18:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 16:23 [RFC] ext2 and ext3 block reservations can be bypassed Kasper Dupont
2002-05-12 16:42 ` Jakob Østergaard
2002-05-12 17:34 ` Elladan
2002-05-12 18:15 ` Alexander Viro
2002-05-12 18:37 ` Elladan
2002-05-12 19:02 ` Jakob Østergaard
2002-05-12 19:04 ` Mark Mielke
2002-05-13 17:09 ` Horst von Brand
2002-05-13 17:52 ` Elladan
2002-05-13 17:57 ` Christoph Hellwig
2002-05-14 16:22 ` Elladan
2002-05-14 16:55 ` Mark Mielke
2002-05-14 17:47 ` Elladan
2002-05-14 18:51 ` Kasper Dupont
2002-05-15 19:48 ` Pavel Machek
2002-05-15 20:29 ` Alan Cox
2002-05-14 15:40 ` Kasper Dupont
2002-05-14 15:56 ` Mark Mielke
2002-05-14 18:25 ` Kasper Dupont [this message]
[not found] <791836807@toto.iv>
2002-05-12 22:04 ` Peter Chubb
2002-05-12 22:53 ` Alexander Viro
2002-05-13 4:22 ` Kasper Dupont
2002-05-13 4:51 ` Elladan
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 17:53 Jesse Pollard
2002-05-14 18:23 ` Mark Mielke
2002-05-14 19:11 ` Alexander Viro
2002-05-14 18:00 Jesse Pollard
2002-05-14 18:07 Jesse Pollard
2002-05-14 18:54 Jesse Pollard
2002-05-14 19:04 ` Alexander Viro
2002-05-14 19:55 ` Mark Mielke
2002-05-14 19:29 Jesse Pollard
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=3CE15684.989AB0D3@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
/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