reiserfs one user DoS?
Hi!
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?
Signature · 2 lines
WBR, Max A. Krasilnikov "Colocall" Internet Data Center
Quoted 13 lines · Max A. Krasilnikov
Hi!
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.;-)
Signature · 1 line
Hans
Quoted 11 lines · Hans Reiser
Quoted 9 lines · Max A. Krasilnikov
Hi!
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.
Quoted 5 lines
Quoted 4 lines
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.
man bash-builtins, search for "ulimit" then.
Christian.
Signature · 3 lines
BOFH excuse #153: Big to little endian conversion error
Quoted 10 lines · Christian Kujau
Quoted 9 lines · Hans Reiser
Quoted 9 lines
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.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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?
Quoted 13 lines · Erik Tews
Quoted 12 lines · Christian Kujau
Quoted 11 lines · Hans Reiser
Quoted 11 lines
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?
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
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.
Quoted 11 lines · Mike Fedyk
Quoted 10 lines · Erik Tews
Quoted 9 lines · Christian Kujau
Quoted 8 lines · Hans Reiser
Quoted 8 lines
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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Quoted 6 lines
Quoted 2 lines
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.
Hello!
Quoted 6 lines · Max A. Krasilnikov
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