2017-02-26 08:26:09 |
jbruijn |
bug |
|
|
added bug |
2017-02-27 14:23:26 |
Christian Ehrhardt |
bug |
|
|
added subscriber Nish Aravamudan |
2017-02-27 21:28:36 |
Nish Aravamudan |
bug watch added |
|
http://bugs.php.net/bug.php?id=74179 |
|
2017-02-28 00:00:20 |
Nish Aravamudan |
description |
I'm running a web application serving rather big binary blobs from a MariaDB table. After the unattended update (7.0.8-0ubuntu0.16.04.3 to 7.0.15-0ubuntu0.16.04.2), the application would routinely break while trying to fetch a >16Mbyte row from the database server.
Requests resulting in a row under 16Mbyte are processed normally, anything above it would return columns in the wrong order, and right around 0xFFFFF2 a null-character (0x00) is inserted into the stream (when the resulting file is compared to one served with the version used previously)
Rolling back to 7.0.4-7ubuntu2 immediately fixed the issue. I'm pretty sure the problem was introduced somewhere between 7.0.8 and 7.0.15, but I cant find anything relevant in the changelog for those versions.
Please let me know what I can do to assist! |
[Impact]
* The prior SRU of 7.0.15 included an upstream regression to MySQL support with large blobs.
* The fix has not yet been published in an upstream release, but is planned for 7.0.17.
[Test Case]
- Ubuntu 16.04
- MariaDB Server (not tested on mysql, but I expect similar results)
- php 7.0 (7.0.15)
- phpMyAdmin
Configuration:
MariaDB: max_allowed_packet = 128M
php: post_max_size and upload_max_filesize raised to 128M
Import some SQL data, for instance: https://we.tl/vb37KISpUU.
This will build you a MyISAM table with 4 columns, 3x varchar(1) and 1 longblob. The table will have one big blob in it, with 32Mbyte worth of 0x20 (space)
Downloading the binary through phpMyAdmin on 7.0.15 will produce a file with a null-character inserted at (for my setup) 0xFFFFF6, the rest of the file is as expected.
[Regression Potential]
* This upload includes the upstream fix, as well as testcases for the same. As this is a fix to an existing regression, I do not believe there is any chance of regression and it should be caught by the test sutie.
---
I'm running a web application serving rather big binary blobs from a MariaDB table. After the unattended update (7.0.8-0ubuntu0.16.04.3 to 7.0.15-0ubuntu0.16.04.2), the application would routinely break while trying to fetch a >16Mbyte row from the database server.
Requests resulting in a row under 16Mbyte are processed normally, anything above it would return columns in the wrong order, and right around 0xFFFFF2 a null-character (0x00) is inserted into the stream (when the resulting file is compared to one served with the version used previously)
Rolling back to 7.0.4-7ubuntu2 immediately fixed the issue. I'm pretty sure the problem was introduced somewhere between 7.0.8 and 7.0.15, but I cant find anything relevant in the changelog for those versions.
Please let me know what I can do to assist! |
|
2017-02-28 21:29:10 |
Nish Aravamudan |
php7.0 (Ubuntu): status |
New |
Fix Committed |
|
2017-02-28 21:29:15 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Xenial |
|
2017-02-28 21:29:15 |
Nish Aravamudan |
bug task added |
|
php7.0 (Ubuntu Xenial) |
|
2017-02-28 21:29:15 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Yakkety |
|
2017-02-28 21:29:15 |
Nish Aravamudan |
bug task added |
|
php7.0 (Ubuntu Yakkety) |
|
2017-02-28 21:29:58 |
Nish Aravamudan |
description |
[Impact]
* The prior SRU of 7.0.15 included an upstream regression to MySQL support with large blobs.
* The fix has not yet been published in an upstream release, but is planned for 7.0.17.
[Test Case]
- Ubuntu 16.04
- MariaDB Server (not tested on mysql, but I expect similar results)
- php 7.0 (7.0.15)
- phpMyAdmin
Configuration:
MariaDB: max_allowed_packet = 128M
php: post_max_size and upload_max_filesize raised to 128M
Import some SQL data, for instance: https://we.tl/vb37KISpUU.
This will build you a MyISAM table with 4 columns, 3x varchar(1) and 1 longblob. The table will have one big blob in it, with 32Mbyte worth of 0x20 (space)
Downloading the binary through phpMyAdmin on 7.0.15 will produce a file with a null-character inserted at (for my setup) 0xFFFFF6, the rest of the file is as expected.
[Regression Potential]
* This upload includes the upstream fix, as well as testcases for the same. As this is a fix to an existing regression, I do not believe there is any chance of regression and it should be caught by the test sutie.
---
I'm running a web application serving rather big binary blobs from a MariaDB table. After the unattended update (7.0.8-0ubuntu0.16.04.3 to 7.0.15-0ubuntu0.16.04.2), the application would routinely break while trying to fetch a >16Mbyte row from the database server.
Requests resulting in a row under 16Mbyte are processed normally, anything above it would return columns in the wrong order, and right around 0xFFFFF2 a null-character (0x00) is inserted into the stream (when the resulting file is compared to one served with the version used previously)
Rolling back to 7.0.4-7ubuntu2 immediately fixed the issue. I'm pretty sure the problem was introduced somewhere between 7.0.8 and 7.0.15, but I cant find anything relevant in the changelog for those versions.
Please let me know what I can do to assist! |
SRU team: as this is a SRU and security regression, I'm hopeful we can bypass the 7-day waiting period, presuming @jbruijn or I can test the version from -proposed first.
[Impact]
* The prior SRU of 7.0.15 included an upstream regression to MySQL support with large blobs.
* The fix has not yet been published in an upstream release, but is planned for 7.0.17.
[Test Case]
- Ubuntu 16.04
- MariaDB Server (not tested on mysql, but I expect similar results)
- php 7.0 (7.0.15)
- phpMyAdmin
Configuration:
MariaDB: max_allowed_packet = 128M
php: post_max_size and upload_max_filesize raised to 128M
Import some SQL data, for instance: https://we.tl/vb37KISpUU.
This will build you a MyISAM table with 4 columns, 3x varchar(1) and 1 longblob. The table will have one big blob in it, with 32Mbyte worth of 0x20 (space)
Downloading the binary through phpMyAdmin on 7.0.15 will produce a file with a null-character inserted at (for my setup) 0xFFFFF6, the rest of the file is as expected.
[Regression Potential]
* This upload includes the upstream fix, as well as testcases for the same. As this is a fix to an existing regression, I do not believe there is any chance of regression and it should be caught by the test sutie.
---
I'm running a web application serving rather big binary blobs from a MariaDB table. After the unattended update (7.0.8-0ubuntu0.16.04.3 to 7.0.15-0ubuntu0.16.04.2), the application would routinely break while trying to fetch a >16Mbyte row from the database server.
Requests resulting in a row under 16Mbyte are processed normally, anything above it would return columns in the wrong order, and right around 0xFFFFF2 a null-character (0x00) is inserted into the stream (when the resulting file is compared to one served with the version used previously)
Rolling back to 7.0.4-7ubuntu2 immediately fixed the issue. I'm pretty sure the problem was introduced somewhere between 7.0.8 and 7.0.15, but I cant find anything relevant in the changelog for those versions.
Please let me know what I can do to assist! |
|
2017-03-01 01:40:43 |
Launchpad Janitor |
php7.0 (Ubuntu): status |
Fix Committed |
Fix Released |
|
2017-03-01 15:56:02 |
Marc Deslauriers |
php7.0 (Ubuntu Xenial): assignee |
|
Marc Deslauriers (mdeslaur) |
|
2017-03-01 15:56:05 |
Marc Deslauriers |
php7.0 (Ubuntu Yakkety): assignee |
|
Marc Deslauriers (mdeslaur) |
|
2017-03-01 15:56:39 |
Marc Deslauriers |
php7.0 (Ubuntu Xenial): status |
New |
Confirmed |
|
2017-03-01 15:56:42 |
Marc Deslauriers |
php7.0 (Ubuntu Yakkety): status |
New |
Confirmed |
|
2017-03-02 09:05:12 |
Łukasz Zemczak |
php7.0 (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
2017-03-02 09:05:14 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2017-03-02 09:05:16 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
2017-03-02 09:05:21 |
Łukasz Zemczak |
tags |
|
verification-needed |
|
2017-03-02 09:06:02 |
Łukasz Zemczak |
php7.0 (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
2017-03-02 11:20:08 |
jbruijn |
tags |
verification-needed |
verification-done |
|
2017-03-02 14:32:09 |
Launchpad Janitor |
php7.0 (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
2017-03-02 14:32:10 |
Launchpad Janitor |
php7.0 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|