lkml.org 
[lkml]   [2007]   [Jan]   [18]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateThu, 18 Jan 2007 17:10:34 +0800
FromJoe Jin <>
SubjectWhy not set siginfo at do_general_protection()?
Hi,

I have a question, while a general protection occured, do_general_protection()
should be called, to other faults, it always set siginfo struct, but at this  
function, it just send a SIGSEGV by force_sig() call but not create a siginfo
struct, at send_signal(), it check the siginfo's value and create the siginfo,
then set siginfo->si_code to SI_KERNEL, but to SIGSEGV signal, the si_code 
should be SEGV_MAPERR or SEGV_ACCERR, to application, it will receive a 
siginfo which si_code is SI_KERNEL, so, why not check the details of fault, 
and set the corresponding value?

Would you pls give me any advices?

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

\
 
 \ /
  Last update: 2007-01-18 11:09    [from the cache]
©2003-2008