From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 3/3] f2fs-tools: fix build failure on mac
Date: Thu, 2 Jul 2026 06:56:02 +0000 [thread overview]
Message-ID: <20260702065602.4120914-3-jaegeuk@kernel.org> (raw)
In-Reply-To: <20260702065602.4120914-1-jaegeuk@kernel.org>
external/f2fs-tools/lib/libf2fs.c:1019:12: error: use of undeclared identifier 'BLKFLSBUF'
1019 | ioctl(fd, BLKFLSBUF);
| ^~~~~~~~~
Fixes: c188a3e303d9 ("f2fs-tools: invalidate block device page cache before reading metadata")
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
lib/libf2fs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/libf2fs.c b/lib/libf2fs.c
index 7f8b643d117d..93f36ca6a30c 100644
--- a/lib/libf2fs.c
+++ b/lib/libf2fs.c
@@ -1016,8 +1016,9 @@ int get_device_info(int i)
}
dev->fd = fd;
+#ifdef BLKFLSBUF
ioctl(fd, BLKFLSBUF);
-
+#endif
if (c.sparse_mode && i == 0) {
if (f2fs_init_sparse_file()) {
free(stat_buf);
--
2.55.0.rc0.799.gd6f94ed593-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-07-02 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:56 [f2fs-dev] [PATCH 1/3] f2fs-tools: Build f2fs-tools with _FILE_OFFSET_BITS=64 Jaegeuk Kim via Linux-f2fs-devel
2026-07-02 6:56 ` [f2fs-dev] [PATCH 2/3] f2fs_io: add include dir Jaegeuk Kim via Linux-f2fs-devel
2026-07-02 7:31 ` Chao Yu via Linux-f2fs-devel
2026-07-02 6:56 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2026-07-02 7:31 ` [f2fs-dev] [PATCH 3/3] f2fs-tools: fix build failure on mac Chao Yu via Linux-f2fs-devel
2026-07-02 7:31 ` [f2fs-dev] [PATCH 1/3] f2fs-tools: Build f2fs-tools with _FILE_OFFSET_BITS=64 Chao Yu via Linux-f2fs-devel
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=20260702065602.4120914-3-jaegeuk@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@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