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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAPDOMVh_AjUwGt5woz7sipFw=fVusbzkoAn1h+eRavN1PbFwFg@mail.gmail.com>
Date:	Thu, 3 Jul 2014 14:17:15 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	Richard Henderson <rth@...ddle.net>
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

In that case I will sent a patch removing this FIXME line.
Cheers Nick

On Thu, Jul 3, 2014 at 2:15 PM, Richard Henderson <rth@...ddle.net> wrote:
> 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/