diff options
| author | Sachin Agarwal <sachin.z.agarwal@oracle.com> | 2018-11-26 16:17:40 +0530 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-04-26 17:40:20 +0300 |
| commit | 06ec56f579e6de647fd38854da31b6324100faf9 (patch) | |
| tree | 14623aabffa37ecf38973e4cdf09cc516aefecea /mysql-test/suite/gcol | |
| parent | 4e9f8c9cc4932db53d5bae456bcdb9f33f822254 (diff) | |
| download | mariadb-git-06ec56f579e6de647fd38854da31b6324100faf9.tar.gz | |
Bug #27850600 INNODB ASYNC IO ERROR HANDLING IN IO_EVENT
Problem:
io_getevents() - read asynchronous I/O events from the completion
queue. For each IO event, the res field in io_event tells whether IO
event is succeeded or not. To see if the IO actually succeeded we
always need to check event.res (negative=error,
positive=bytesread/written).
LinuxAIOHandler::collect() doesn't check event.res value for each event.
which leads to incorrect value in n_bytes for IO context (or IO Slot).
Fix:
Added a check for event.res negative value.
RB: 20871
Reviewed by : annamalai.gurusami@oracle.com
Diffstat (limited to 'mysql-test/suite/gcol')
0 files changed, 0 insertions, 0 deletions