[MDEV-7143] mysql load --local-infile sends unknown 4-byte packet Created: 2014-11-19 Updated: 2014-12-17 Resolved: 2014-12-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 5.5.33a |
| Fix Version/s: | 5.5.41 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Vilho Raatikka | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
64-bit linux |
||
| Description |
|
I see extra bytes in what mysql client sends to server when load data local infile .. is called. The extra bytes appears to be an additional packet which I don't recognize to any known packet. It consists of 4 bytes and includes 0x0 0x0 0x0 0x3 . ngrep dump caught by exexcuting :
dump:
|
| Comments |
| Comment by Vilho Raatikka [ 2014-11-20 ] |
|
MySQL client : mysql Ver 15.1 Distrib 5.5.37-MariaDB, for Linux (x86_64) using readline 5.1 Content of load3.txt : |
| Comment by Nirbhay Choubey (Inactive) [ 2014-12-17 ] |
|
vilho That's an empty packet which client sends after it has sent the INFILE contents. An empty packet only has header and no payload, http://dev.mysql.com/doc/internals/en/com-query-response.html#packet-Protocol::LOCAL_INFILE_Request |
| Comment by Vilho Raatikka [ 2014-12-17 ] |
|
Is the LOAD INFILE protocol and the empty packet documented somewhere? |
| Comment by Nirbhay Choubey (Inactive) [ 2014-12-17 ] |
|
Yes, check the link in my previous comment. |