Actions
Bug #57766
closed[test] fio 3.16 doesn't build on recent kernels due to removal of linux/raw.h
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
2022-10-04T22:02:50.819 DEBUG:teuthology.orchestra.run.smithi182:> cd /home/ubuntu/cephtest/rbd_fio_test ; wget https://github.com/axboe/fio/archive/fio-3.16.tar.gz ; tar -xvf fio*tar.gz ; cd fio-fio* ; ./configure ; make
2022-10-04T22:02:56.232 INFO:teuthology.orchestra.run.smithi182.stdout: CC crc/crc32c-arm64.o 2022-10-04T22:02:56.284 INFO:teuthology.orchestra.run.smithi182.stderr:In file included from crc/../os/os.h:38, 2022-10-04T22:02:56.285 INFO:teuthology.orchestra.run.smithi182.stderr: from crc/crc32c-arm64.c:2: 2022-10-04T22:02:56.285 INFO:teuthology.orchestra.run.smithi182.stderr:crc/../os/os-linux.h:17:10: fatal error: linux/raw.h: No such file or directory 2022-10-04T22:02:56.285 INFO:teuthology.orchestra.run.smithi182.stderr: 17 | #include <linux/raw.h> 2022-10-04T22:02:56.285 INFO:teuthology.orchestra.run.smithi182.stderr: | ^~~~~~~~~~~~~ 2022-10-04T22:02:56.286 INFO:teuthology.orchestra.run.smithi182.stderr:compilation terminated. 2022-10-04T22:02:56.288 INFO:teuthology.orchestra.run.smithi182.stderr:make: *** [Makefile:375: crc/crc32c-arm64.o] Error 1
linux/raw.h was removed in kernel 5.14:
and picked up in fio 3.28:
https://github.com/axboe/fio/commit/382975557e632efb506836bc1709789e615c9094
Updated by Ilya Dryomov over 1 year ago
- Status changed from In Progress to Fix Under Review
- Backport set to pacific,quincy
- Pull request ID set to 48372
Updated by Ilya Dryomov over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 1 year ago
- Copied to Backport #57779: quincy: [test] fio 3.16 doesn't build on recent kernels due to removal of linux/raw.h added
Updated by Backport Bot over 1 year ago
- Copied to Backport #57780: pacific: [test] fio 3.16 doesn't build on recent kernels due to removal of linux/raw.h added
Updated by Backport Bot over 1 year ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions