| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: epoll_wait returning EFAULT on Linux 3.2.78 |
| Date: | 2016-06-02 14:49:38 |
| Message-ID: | 20160602144938.5fqi6kuhmqrm3tnc@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2016-06-02 15:31:15 +0100, Greg Stark wrote:
> What I'm seeing is that every call to epoll_wait() raises EFAULT. I
> don't see anything wrong with the arguments to epoll_wait so unless
> there was some earlier bogus argument to epoll_ctl or something this
> looks like some kind of kernel or glibc problem and it looks like
> we'll to check for EFAULT and fall back to poll (a configure test
> wouldn't help since this is run-time behaviour).
I'd really like knowing what's going on before doing that. epoll was
definitely supported back then, and just falling back to poll seems too
likely to be just papering over bug or portability issue on our side.
Any chance you could provide a strace of a problematic sequence?
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-02 14:50:20 | Re: epoll_wait returning EFAULT on Linux 3.2.78 |
| Previous Message | Konstantin Knizhnik | 2016-06-02 14:42:28 | Re: array of domain types |