[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Kernel stack for a process



> You have a nice big smoking crater in the landscape. Kernel
> code is carefully written to avoid deep call nesting.

Hmmm i had thaught of this.

but consider this:
suppose im traversing the simlinks.
there could be thousands of nested links ( in my dreamland ).
( im not tellin abt self loops, which could be detected.
  but actual nested links. )
Then system may go in spinloop.

What im tryin to point out is that this could be a loophole for
a dirty user ( like me ! ).
What i would do is, create 1000 symlinks in my program.
( this isnt a dream !). And use "symlinks" for resolving it.  or write my
own recursive
simlink extraction program. Thats it. Im a normal user and able to crash
the server !

What could be a workaround for this kinda things ?
Is it comin up in next kernel releases ??

enlighten me plz..

-nagaraj

-(*_*)-








--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/