LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Why not set siginfo at do_general_protection()?
@ 2007-01-18 9:10 Joe Jin
0 siblings, 0 replies; only message in thread
From: Joe Jin @ 2007-01-18 9:10 UTC (permalink / raw)
To: gareth, torvalds; +Cc: linux-kernel
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-01-18 9:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-01-18 9:10 Why not set siginfo at do_general_protection()? Joe Jin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).