From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Failed to compile due to missing <linux/blkdev.h> header with liburing-2.9?
Date: Sat, 8 Feb 2025 14:13:23 +1030 [thread overview]
Message-ID: <b7149d6f-2c1b-4c51-ac0c-0b2d7560330c@gmx.com> (raw)
Hi,
Just find out that fsstress no longer compiles on for-next (v2025.02.02)
, patches-in-queue (a494849fb48dc6b276c2a1784d6ff66c731e5572) nor master
branchs (8467552f09e1672a02712653b532a84bd46ea10e)
All fails with the following error:
```
Building ltp
[CC] fsstress
In file included from /usr/include/liburing.h:17,
from fsstress.c:30:
/usr/include/liburing/compat.h:11:10: fatal error: linux/blkdev.h: No
such file or directory
11 | #include <linux/blkdev.h>
| ^~~~~~~~~~~~~~~~
```
This seems to be a change in the liburing headers, as v2.8 still
compiles fine.
Is there something wrong with header change?
Thanks,
Qu
next reply other threads:[~2025-02-08 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 3:43 Qu Wenruo [this message]
2025-02-08 13:11 ` Failed to compile due to missing <linux/blkdev.h> header with liburing-2.9? Jens Axboe
2025-02-08 20:40 ` Qu Wenruo
2025-02-08 22:08 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7149d6f-2c1b-4c51-ac0c-0b2d7560330c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=axboe@kernel.dk \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox