Re: Kernel stack....

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

 



Hi,

Ralph Corderoy wrote:

> Hi,
>
> Is there any mechanism to detect the stack growing down and trampling
> the process descriptor?

As far as I know there isn't. At least you can easily crash your computer by overflowing the kernel stack. The attached module does the job. I also attach the kernel
messages I get on an Alpha SMP machine, when running the module.

regards
Martin


--
Supercomputing System AG          email: maletinsky@scs.ch
Martin Maletinsky                 phone: +41 (0)1 445 16 05
Technoparkstrasse 1               fax:   +41 (0)1 445 16 10
CH-8005 Zurich

X bitmap

call/depth 815
call/depth 816
call/depth 817
call/depth 818
call/depth 819
call/depth 820
call/depth 821
call/depth 822
call/depth 823
call/depth 824
call/depth 825
call/depth 826
call/depth 827
CPU 0 (17266): Instruction fault 3
pc = [<fffffc00003107b0>]  ra = [<fffffc000032014c>]  ps = 0000
v0 = 000000001eae85b0  t0 = fffffc0000310a70  t1 = 0000000000000001
 
halted CPU 0
CPU 1 is not halted
 
halt code = 4
invalid PTBR
PC = fffffc0000331060              

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux