* [ruby-core:61357] [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
@ 2014-03-07 9:55 ` normalperson
2014-03-30 3:28 ` [ruby-core:61761] " Eric Wong
2014-03-07 9:57 ` [ruby-core:61358] [ruby-trunk - Bug #9608] " normalperson
` (4 subsequent siblings)
5 siblings, 1 reply; 7+ messages in thread
From: normalperson @ 2014-03-07 9:55 UTC (permalink / raw
To: ruby-core
Issue #9608 has been reported by Eric Wong.
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608
* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
--
http://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:61358] [ruby-trunk - Bug #9608] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
2014-03-07 9:55 ` [ruby-core:61357] [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls normalperson
@ 2014-03-07 9:57 ` normalperson
2014-03-30 3:38 ` [ruby-core:61762] " normalperson
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: normalperson @ 2014-03-07 9:57 UTC (permalink / raw
To: ruby-core
Issue #9608 has been updated by Eric Wong.
File 0001-avoid-large-alloca-on-Complex-Rational-calls.patch added
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608#change-45677
* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
---Files--------------------------------
0001-avoid-large-alloca-on-Complex-Rational-calls.patch (1.86 KB)
--
http://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:61761] Re: [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls
2014-03-07 9:55 ` [ruby-core:61357] [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls normalperson
@ 2014-03-30 3:28 ` Eric Wong
0 siblings, 0 replies; 7+ messages in thread
From: Eric Wong @ 2014-03-30 3:28 UTC (permalink / raw
To: ruby-core
tadf: ping?
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:61762] [ruby-trunk - Bug #9608] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
2014-03-07 9:55 ` [ruby-core:61357] [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls normalperson
2014-03-07 9:57 ` [ruby-core:61358] [ruby-trunk - Bug #9608] " normalperson
@ 2014-03-30 3:38 ` normalperson
2014-05-02 11:29 ` [ruby-core:62292] " tadf
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: normalperson @ 2014-03-30 3:38 UTC (permalink / raw
To: ruby-core
Issue #9608 has been updated by Eric Wong.
tadf: ping?
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608#change-45995
* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
---Files--------------------------------
0001-avoid-large-alloca-on-Complex-Rational-calls.patch (1.86 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:62292] [ruby-trunk - Bug #9608] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
` (2 preceding siblings ...)
2014-03-30 3:38 ` [ruby-core:61762] " normalperson
@ 2014-05-02 11:29 ` tadf
2014-06-27 8:13 ` [ruby-core:63358] " usa
2014-06-29 17:21 ` [ruby-core:63403] " nagachika00
5 siblings, 0 replies; 7+ messages in thread
From: tadf @ 2014-05-02 11:29 UTC (permalink / raw
To: ruby-core
Issue #9608 has been updated by tadayoshi funaba.
i'd like to try it; please commit it.
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608#change-46456
* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
---Files--------------------------------
0001-avoid-large-alloca-on-Complex-Rational-calls.patch (1.86 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:63358] [ruby-trunk - Bug #9608] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
` (3 preceding siblings ...)
2014-05-02 11:29 ` [ruby-core:62292] " tadf
@ 2014-06-27 8:13 ` usa
2014-06-29 17:21 ` [ruby-core:63403] " nagachika00
5 siblings, 0 replies; 7+ messages in thread
From: usa @ 2014-06-27 8:13 UTC (permalink / raw
To: ruby-core
Issue #9608 has been updated by Usaku NAKAMURA.
Backport changed from 1.9.3: UNKNOWN, 2.0.0: REQUIRED, 2.1: REQUIRED to 1.9.3: UNKNOWN, 2.0.0: DONE, 2.1: REQUIRED
backported into `ruby_2_0_0` at r46578.
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608#change-47409
* Author: Eric Wong
* Status: Closed
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: DONE, 2.1: REQUIRED
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
---Files--------------------------------
0001-avoid-large-alloca-on-Complex-Rational-calls.patch (1.86 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [ruby-core:63403] [ruby-trunk - Bug #9608] [PATCH] avoid large alloca on Complex/Rational calls
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
` (4 preceding siblings ...)
2014-06-27 8:13 ` [ruby-core:63358] " usa
@ 2014-06-29 17:21 ` nagachika00
5 siblings, 0 replies; 7+ messages in thread
From: nagachika00 @ 2014-06-29 17:21 UTC (permalink / raw
To: ruby-core
Issue #9608 has been updated by Tomoyuki Chikanaga.
Backport changed from 1.9.3: UNKNOWN, 2.0.0: DONE, 2.1: REQUIRED to 1.9.3: UNKNOWN, 2.0.0: DONE, 2.1: DONE
Backported into `ruby_2_1` at r46612.
----------------------------------------
Bug #9608: [PATCH] avoid large alloca on Complex/Rational calls
https://bugs.ruby-lang.org/issues/9608#change-47446
* Author: Eric Wong
* Status: Closed
* Priority: Normal
* Assignee: tadayoshi funaba
* Category: core
* Target version:
* ruby -v: ruby 2.2.0dev (2014-03-07 trunk 45281) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: DONE, 2.1: DONE
----------------------------------------
* complex.c (parse_comp): replace ALLOCA_N with ALLOCV_N/ALLOCV_END
* rational.c (read_digits): ditto
This fixes segfaults on:
Rational("1" * 16 * 1024 * 1024)
Complex("1" * 16 * 1024 * 1024)
On my system where my stack size is only 8M.
tadf: Should we raise an exception on large string instead?
Large strings are slow to parse and could still be a DoS.
---Files--------------------------------
0001-avoid-large-alloca-on-Complex-Rational-calls.patch (1.86 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-06-29 17:01 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-9608.20140307095559@ruby-lang.org>
2014-03-07 9:55 ` [ruby-core:61357] [ruby-trunk - Bug #9608] [Open] [PATCH] avoid large alloca on Complex/Rational calls normalperson
2014-03-30 3:28 ` [ruby-core:61761] " Eric Wong
2014-03-07 9:57 ` [ruby-core:61358] [ruby-trunk - Bug #9608] " normalperson
2014-03-30 3:38 ` [ruby-core:61762] " normalperson
2014-05-02 11:29 ` [ruby-core:62292] " tadf
2014-06-27 8:13 ` [ruby-core:63358] " usa
2014-06-29 17:21 ` [ruby-core:63403] " nagachika00
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).