lkml.org 
[lkml]   [1999]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Kernel stack corruption
Date
> the same happens with KIP5_IOCSETSBTCODE functions. 
> Only calls like KIP5_IOCSETSBTSIZE where READ and WRITE flags are not set
> returns without problems.
>
> Can anyone tell me why this happens?

Either you trashed the stack by a buffer overrun or by trying to put too
much on the kernel stack. You really shouldnt be putting blocks bigger than
a couple of K on the stack


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.138 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site