linux-kernel - Re: PATCH - x86-64 signed-compare bug, was Re: select() setting ERESTARTNOHAND (514).

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Jan 2007 21:09:17 -0700
From:	Sean Reifschneider <jafo@...my.com>
To:	Neil Brown <neilb@...e.de>
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: PATCH - x86-64 signed-compare bug, was Re: select() setting ERESTARTNOHAND (514).

On Thu, Jan 11, 2007 at 12:02:53PM +1100, Neil Brown wrote:
>On Thursday January 11, ak@...e.de wrote:
>> Normally it should be only visible in strace. Did you see it without
>> strace?
>
>No, only in strace.

I am absolutely seeing it outside of strace.  It is showing up as an errno
to the select call:

   if (select(0, (fd_set *)0, (fd_set *)0, (fd_set *)0, &t) != 0) {
      if (errno != EINTR) {
         PyErr_SetFromErrno(PyExc_IOError);
         return -1;
      }

This code is seeing errno=514.

>> > You don't mention in the Email which kernel version you use but I see
>> > from the web page you reference it is 2.6.19.1.  I'm using

The production system is running CentOS 4.4, 2.6.9 kernel.  However, it
looks to be the same issue all the way up to 2.6.19.1, and google shows
reports of it on 2.6.17.

Thanks,
Sean
-- 
 George Washington was first in war, first in peace -- and first to
 have his birthday juggled to make a long weekend.
Sean Reifschneider, Member of Technical Staff <jafo@...my.com>
tummy.com, ltd. - Linux Consulting since 1995: Ask me about High Availability

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