linux-kernel - Re: epoll handling in the alpha port

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:	Fri, 2 Feb 2007 00:19:35 -0500
From:	Mike Frysinger <vapier@...too.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	rth@...ddle.net, linux-kernel@...r.kernel.org, alpha@...too.org
Subject: Re: epoll handling in the alpha port

On Friday 02 February 2007, Andrew Morton wrote:
> It might be to late to fix this - we risk breaking userspace which worked
> around it.

we'd be breaking userspace API, but not ABI ... and the largest consumers out 
there (glibc/uclibc) have not been accounting for this, so we wouldnt be 
breaking them

that's how we noticed the issue in Gentoo ... all the epoll calls are 
automatically declared -ENOSYS stubs in glibc's libc.so

is there some other large consumer i'm not thinking of ?

> It would be safer to add the correct definitions while leaving the old ones
> in place.

in the end, either works for me ... i can see linux's pretty hard 'dont break 
userspace' policy coming into play here
-mike
-
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/