linux-kernel - Why not set siginfo at do_general

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20070118091034.GA5826@joejin-pc.cn.oracle.com>
Date:	Thu, 18 Jan 2007 17:10:34 +0800
From:	Joe Jin <joe.jin@...cle.com>
To:	gareth@...inux.com, torvalds@...l.org
Cc:	linux-kernel@...r.kernel.org
Subject: Why 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/