From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Subject: [PATCH] fsverity: explicitly include <linux/export.h>
Date: Sat, 14 Jun 2025 15:17:23 -0700 [thread overview]
Message-ID: <20250614221723.131827-1-ebiggers@kernel.org> (raw)
From: Eric Biggers <ebiggers@google.com>
Fix build warnings with W=1 that started appearing after
commit a934a57a42f6 ("scripts/misc-check: check missing #include
<linux/export.h> when W=1").
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
This patch applies to v6.16-rc1 and is targeting fsverity/for-next
fs/verity/enable.c | 1 +
fs/verity/measure.c | 1 +
fs/verity/open.c | 1 +
fs/verity/read_metadata.c | 1 +
fs/verity/verify.c | 1 +
5 files changed, 5 insertions(+)
diff --git a/fs/verity/enable.c b/fs/verity/enable.c
index c284f46d1b535..9b335bee88a5a 100644
--- a/fs/verity/enable.c
+++ b/fs/verity/enable.c
@@ -6,10 +6,11 @@
*/
#include "fsverity_private.h"
#include <crypto/hash.h>
+#include <linux/export.h>
#include <linux/mount.h>
#include <linux/sched/signal.h>
#include <linux/uaccess.h>
struct block_buffer {
diff --git a/fs/verity/measure.c b/fs/verity/measure.c
index 175d2f1bc0893..388734132f018 100644
--- a/fs/verity/measure.c
+++ b/fs/verity/measure.c
@@ -7,10 +7,11 @@
#include "fsverity_private.h"
#include <linux/bpf.h>
#include <linux/btf.h>
+#include <linux/export.h>
#include <linux/uaccess.h>
/**
* fsverity_ioctl_measure() - get a verity file's digest
* @filp: file to get digest of
diff --git a/fs/verity/open.c b/fs/verity/open.c
index fdeb95eca3af3..ac2c99fbf37b9 100644
--- a/fs/verity/open.c
+++ b/fs/verity/open.c
@@ -5,10 +5,11 @@
* Copyright 2019 Google LLC
*/
#include "fsverity_private.h"
+#include <linux/export.h>
#include <linux/mm.h>
#include <linux/slab.h>
static struct kmem_cache *fsverity_info_cachep;
diff --git a/fs/verity/read_metadata.c b/fs/verity/read_metadata.c
index f58432772d9ea..cba5d6af4e04f 100644
--- a/fs/verity/read_metadata.c
+++ b/fs/verity/read_metadata.c
@@ -6,10 +6,11 @@
*/
#include "fsverity_private.h"
#include <linux/backing-dev.h>
+#include <linux/export.h>
#include <linux/highmem.h>
#include <linux/sched/signal.h>
#include <linux/uaccess.h>
static int fsverity_read_merkle_tree(struct inode *inode,
diff --git a/fs/verity/verify.c b/fs/verity/verify.c
index 4fcad0825a120..14520289093ca 100644
--- a/fs/verity/verify.c
+++ b/fs/verity/verify.c
@@ -7,10 +7,11 @@
#include "fsverity_private.h"
#include <crypto/hash.h>
#include <linux/bio.h>
+#include <linux/export.h>
static struct workqueue_struct *fsverity_read_workqueue;
/*
* Returns true if the hash block with index @hblock_idx in the tree, located in
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.49.0
next reply other threads:[~2025-06-14 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 22:17 Eric Biggers [this message]
2025-06-17 3:24 ` [PATCH] fsverity: explicitly include <linux/export.h> Eric Biggers
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=20250614221723.131827-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.