From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Xi Wang <xi(dot)wang(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [RFC] overflow checks optimized away |
Date: | 2013-07-15 22:16:06 |
Message-ID: | CA+TgmoY5cBTZQYktT65iOYMccZgZj_G4Qk1x-553P3MGfar0bQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 15, 2013 at 5:59 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Xi Wang escribió:
>> Intel's icc and PathScale's pathcc compilers optimize away several
>> overflow checks, since they consider signed integer overflow as
>> undefined behavior. This leads to a vulnerable binary.
>
> This thread died without reaching a conclusion. Noah Misch, Robert Haas
> and Greg Stark each gave a +1 to the patches, but Tom Lane gave them a
> -inf; so they weren't applied. However, I think everyone walked away
> with the feeling that Tom is wrong on this.
>
> Meanwhile Xi Wang and team published a paper:
> http://pdos.csail.mit.edu/~xi/papers/stack-sosp13.pdf
>
> Postgres is mentioned a number of times in this paper -- mainly to talk
> about the bugs we leave unfixed.
>
> It might prove useful to have usable these guys' STACK checker output
> available continuously, so that if we happen to introduce more bugs in
> the future, it alerts us about that.
Yeah, I think we ought to apply those patches. I don't suppose you
have links handy?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-07-15 22:19:27 | Re: [RFC] overflow checks optimized away |
Previous Message | Alvaro Herrera | 2013-07-15 21:59:50 | Re: [RFC] overflow checks optimized away |