linux-kernel - Re: FIX ME message in osf

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 for Android: free password hash cracker in your pocket

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

Message-ID: <53B59DC2.20809@twiddle.net>
Date:	Thu, 03 Jul 2014 11:15:30 -0700
From:	Richard Henderson <rth@...ddle.net>
To:	Nick Krause <xerofoify@...il.com>
CC:	ink@...assic.park.msu.ru, Matt Turner <mattst88@...il.com>,
	linux-alpha@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: FIX ME message in osf_sys.c

On 07/03/2014 10:21 AM, Nick Krause wrote:
> There seems to be a Fix Me message on line 892 due to info.si_addr = NULL.
> I am wondering what value I should declare this variable to instead of Null.
> Cheers Nick
> 

The closest thing to compatibility with SIGFPE raised through normal arithmetic
would be the address of the instruction after the callsys that lead to this
system call.  Except that's not available without complicating the call to
osf_setsysinfo, and it doesn't seem worth it.


r~
--
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/