summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Correct date of releaseSawyer X2018-11-021-1/+1
| | | | (cherry picked from commit 1b78d74c75ae11feaa8fb945d8e890c1ba838384)
* Bump againSawyer X2018-11-021-1/+1
| | | | (manually cherry picked from commit 0b7d542bdffc479f173119edb2e43477c8a4f5c7)
* Update Module::CoreList for 5.28.0-RC2Sawyer X2018-11-021-1/+1
| | | | (manually cherry picked from commit 4e413ccfa1c5fbbb1d4ad853fa0d87e0fa78c0ea)
* Update Module::CoreList for 5.28.0Sawyer X2018-11-022-3/+3
| | | | (manually cherry picked from commit a0ddfddcc096b9cfc831ab1f7ba80c436820d77e)
* Update Module::CoreList for 5.28.0-RC1Sawyer X2018-11-021-1/+14
| | | | (cherry picked from commit 6087c658568c658774d7eb13037d5d4756b10e6a)
* remove Storable::__Storable__ from Module::CoreListKaren Etheridge2018-11-021-2/+0
| | | | | | | | It was mistakenly picked up starting in 5.27.6 due to ad2ec6b54c and we didn't notice: it should have never been added. Remove historical entries and blacklist it so it doesn't come back. (manually cherry picked from commit 7c07b4b54b42243e151c5943143c0af7c19b29b7)
* Update Module::CoreList for 5.28.0, I hope correctlySawyer X2018-11-021-0/+3
| | | | (manually cherry picked from commit e18dd902dcdeef4ecf095fbbf0c06f83f37011e0)
* Fix Module::CoreList versionsSawyer X2018-11-022-0/+15
| | | | (manually cherry picked from commit 999f678663d12737388c2458d58b37af627911d0)
* Update Module::CoreList for 5.27.11Sawyer X2018-11-022-1/+34
| | | | (manually cherry picked from commit 488fe208c4adb33d486290723ec2d3835247e6e0)
* Adjust code which did not get automatically switched over to 5.027011Todd Rinaldo2018-11-022-0/+22
| | | | | | | | | | The following changes were still required after doing $ ./perl -Ilib Porting/bump-perl-version -i 5.27.10 5.27.11 Module::CoreList had to be updated by hand. (manually cherry picked from commit 26db197235f7e3542da8926da0de654f5fab0845)
* Tick off 5.24.4 and 5.26.2Steve Hay2018-11-021-2/+2
| | | | (cherry picked from commit e5c6bc4adb0873444a9554a01d0e24734f7d2a6e)
* 5.24.4 todaySteve Hay2018-11-021-0/+1
| | | | | (cherry picked from commit 3e87ffef3c714f1b79cd46c90c0f45012290c35b) (cherry picked from commit e5268bc895cb272eced2f3f5b7b415fea063fa47)
* Import perl5244delta.podSteve Hay2018-11-024-0/+136
| | | | (manually cherry picked from commit fb51aa58533593dbb99ea302ea22cfff2a0d8b9d)
* Update Module-CoreList with data for 5.24.4Steve Hay2018-11-023-0/+30
| | | | (manually cherry picked from commit 994c9c8455e5fac563278a15af675ac9b52e92d8)
* (perl #133250) backport CVE-2018-12015 fixTony Cook2018-09-243-1/+18
|
* Create new perldelta for 5.26.3Steve Hay2018-04-1411-119/+544
|
* Epigraphs for 5.24.4 and 5.26.2Steve Hay2018-04-141-0/+31
| | | | (cherry picked from commit 15e2c76df78f6d5fe4a20de12c83453c422a36b9)
* Finalize perldeltav5.26.2Steve Hay2018-04-141-2/+2
|
* 5.26.2 todaySteve Hay2018-04-141-0/+1
|
* Update Module-CoreList for 5.26.2Steve Hay2018-04-141-1/+1
|
* Add epigraphs for 5.24.4-RC1 and 5.26.2-RC1Steve Hay2018-03-241-0/+23
| | | | (cherry picked from commit 811612a11efb1ebc131370e8238d3512779354f8)
* Disarm patchlevel.h and regen META.jsonSteve Hay2018-03-242-2/+1
|
* Update META.jsonv5.26.2-RC1Steve Hay2018-03-241-1/+1
|
* Bump to RC1Steve Hay2018-03-241-0/+1
|
* 5.24.4-RC1 and 5.26.2-RC1 todaySteve Hay2018-03-241-0/+2
| | | | (cherry picked from commit 1f807e151b9979621bcb51f3b884b4daf37b7001)
* Finalize perldeltaSteve Hay2018-03-241-2/+26
|
* perldelta for previous commitSteve Hay2018-03-241-0/+8
|
* PATCH: [perl #132055] Assertion failureKarl Williamson2018-03-241-0/+10
| | | | | | | This checks for and aborts if it find control characters in a supposed Unicode property name. Code further along could not handle these. This also fixes #132553 and #132658
* Add perldelta for 5.24.3Steve Hay2018-03-234-0/+341
| | | | (manually cherry picked from commit c592f515473287ef2f6de4cec0ef64415c5c4960)
* perldelta - Update security fixes sectionSteve Hay2018-03-231-4/+15
|
* (perl #132227) restart a node if we change to uni rules within the node and ↵Karl Williamson2018-03-231-0/+12
| | | | | | | | encounter a sharp S This could lead to a buffer overflow. (cherry picked from commit a02c70e35d1313a5f4e245e8f863c810e991172d)
* utf8.c: Don't dump malformation past first NULKarl Williamson2018-03-231-2/+14
| | | | | | | | | | | | | | | | When a UTF-8 string contains a malformation, the bytes are dumped out as a debugging aid. One should exercise caution, however, and not dump out bytes that are actually past the end of the string. Commit 99a765e9e37 from 2016 added the capability to signal to the dumping routines that we're not sure where the string ends, and to dump the minimal possible. It occurred to me that an additional safety measure can be easily added, which this commit does. And that is, in the dumping routines to stop at the first NUL. All strings automatically get a traiing NUL added, even if they contain embedded NULs. A NUL can never be part of a malformation, and so its presence likely signals the end of the string. (cherry picked from commit d63697aeef46b380c02ba710722c8d94c54ffb63)
* (perl #132063) we should no longer warn for this codeTony Cook2018-03-231-3/+0
| | | | | | | | | | The first patch for 132063 prevented the buffer read overflow when dumping the warning but didn't fix the underlying problem. The next change treats the supplied buffer correctly, preventing the non-UTF-8 SV from being treated as UTF-8, preventing the warning. (cherry picked from commit 137b59d638977222c5de78330aacdcde340fd611)
* 5.26.1: fix TRIE_READ_CHAR and DECL_TRIE_TYPE to account for non-utf8 targetYves Orton2018-03-232-4/+11
| | | | (cherry picked from commit 1924ce1c74248596589210f8a323aa0ceac0bd0d)
* [perl #132063]: Heap buffer overflowKarl Williamson2018-03-232-15/+25
| | | | | | | | | | | The proximal cause is several instances in regexec.c of the code assuming that the input was valid UTF-8, whereas the input was too short for what the start byte claimed it would be. I grepped through the core for any other similar uses, and did not find any. (cherry picked from commit 9a55d25bcb19abb556c14717b222dc81776d0166)
* (perl #131844) fix various space calculation issues in pp_pack.cTony Cook2018-03-232-5/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - for the originally reported case, if the start/cur pointer is in the top 75% of the address space the add (cur) + glen addition would overflow, resulting in the condition failing incorrectly. - the addition of the existing space used to the space needed could overflow, resulting in too small an allocation and a buffer overflow. - the scaling for UTF8 could overflow. - the multiply to calculate the space needed for many items could overflow. For the first case, do a space calculation without making new pointers. For the other cases, detect the overflow and croak if there's an overflow. Originally this used Size_t_MAX as the maximum size of a memory allocation, but for -DDEBUGGING builds realloc() throws a panic for allocations over half the address space in size, changing the error reported for the allocation. For non-DEBUGGING builds the Size_t_MAX limit has the small chance of finding a system that has 3GB of contiguous space available, and allocating that space, which could be a denial of servce in some cases. Unfortunately changing the limit to half the address space means that the exact case with the original issue can no longer occur, so the test is no longer testing against the address + length issue that caused the original problem, since the allocation is failing earlier. One option would be to change the test so the size request by pack is just under 2GB, but this has a higher (but still low) probability that the system has the address space available, and will actually try to allocate the memory, so let's not do that. (cherry picked from commit dc65c7b0b6c825fac12bb9179e9593cbccd26e9f)
* Bump release date to mid-AprilSteve Hay2018-03-225-8/+8
|
* update Module::CoreList for v5.27.10Todd Rinaldo2018-03-222-30/+194
| | | | (manually cherry picked from commit 27ee818c2aa6c1aa9d6223226f7dcb9e4aea75ae)
* Bump Module::CoreListSawyer X2018-03-222-0/+55
| | | | (manually cherry picked from commit 4f01496f3c1a7adbef81d146f9a09e8700d85ed9)
* Epigraph for 5.27.10Todd Rinaldo2018-03-221-0/+11
| | | | (cherry picked from commit ae5389b2505efdb9b72847eb64757aea68e8da52)
* Perlhist entry for 5.27.10Todd Rinaldo2018-03-221-0/+1
| | | | (cherry picked from commit f0282de6e1af44f945ea5d4ec9c7cf6469324731)
* Maint releases are now expected mid-April; RC1s will be out soonSteve Hay2018-03-221-2/+2
| | | | (cherry picked from commit 3a7f897ad3c330a4e99ba46255bb72e89c43cd08)
* Push release of 5.28 by a month to MaySawyer X2018-03-221-4/+5
| | | | (cherry picked from commit 7409ea5bbe81f691ca3a38072887895a24fbe4ed)
* Tick another dev release offChris 'BinGOs' Williams2018-03-221-1/+1
| | | | (cherry picked from commit 33639e64db2cfdd518ebb0f6b0ed8ac26c520a82)
* perldelta - Add bug linkSteve Hay2018-03-221-8/+8
|
* perldelta for bb4e4c3869d9Tony Cook2018-03-221-0/+11
| | | | (cherry picked from commit 084ed71b2c938c47d8ff7e92e8cbd84f598779d3)
* perldelta for #132017 fixJohn SJ Anderson2018-03-221-0/+5
| | | | (manually cherry picked from commit 21741043b5cb549b99b77c99a0e2ea8c037aeb68)
* (perl #125351) abort parsing if parse errors happen in a sub lexSteve Hay2018-03-193-1/+31
| | | | | | | | | | | | | | | | | | We've had a few reports of segmentation faults and other misbehaviour when sub-parsing, such as within interpolated expressions, fails. This change aborts compilation if anything complex enough to not be parsed by the lexer is compiled in a sub-parse *and* an error occurs within the sub-parse. An earlier version of this patch failed on simpler expressions, which caused many test failures, which this version doesn't (which may just mean we need more tests...) (cherry picked from commit bb4e4c3869d9fb6ee5bddd820c2a373601ecc310) Modified for maint by cherry-picker: New parser struct members moved to end of struct to preserve backwards-compatibility.
* fix #132017 - OPFAIL insert needs to set flags to 0Yves Orton2018-03-192-2/+9
| | | | | | why reginsert doesnt do this stuff I dont know. (cherry picked from commit 4dc12118f61b997fbd030230665b46e7c40f32d6)
* perldelta - Update Modules so farSteve Hay2018-03-131-1/+13
|
View Lorry Controller Status