[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkXc0RjJYQoGZZ8A@57de4820519d>
Date: Fri, 1 Apr 2022 00:54:41 +0800
From: kernel test robot <lkp@...el.com>
To: Axel Rasmussen <axelrasmussen@...gle.com>
Cc: kbuild-all@...ts.01.org,
Linux Memory Management List <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH linux-next] mm/secretmem: secretmem_iops can be static
mm/secretmem.c:173:31: warning: symbol 'secretmem_iops' was not declared. Should it be static?
Fixes: 24209f2f4d62 ("mm/secretmem: fix panic when growing a memfd_secret")
Reported-by: kernel test robot <lkp@...el.com>
Signed-off-by: kernel test robot <lkp@...el.com>
---
mm/secretmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/secretmem.c b/mm/secretmem.c
index a83e98aa3a7b3..ddf45c0435be7 100644
--- a/mm/secretmem.c
+++ b/mm/secretmem.c
@@ -170,7 +170,7 @@ static int secretmem_setattr(struct user_namespace *mnt_userns,
return simple_setattr(mnt_userns, dentry, iattr);
}
-const struct inode_operations secretmem_iops = {
+static const struct inode_operations secretmem_iops = {
.setattr = secretmem_setattr,
};
Powered by blists - more mailing lists