LKML Archive on
help / color / mirror / Atom feed
From: Joe Jin <>
Subject: Why not set siginfo at do_general_protection()?
Date: Thu, 18 Jan 2007 17:10:34 +0800	[thread overview]
Message-ID: <> (raw)


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?


                 reply	other threads:[~2007-01-18  9:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Why not set siginfo at do_general_protection()?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).