From nobody Fri Jun 19 16:56:25 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6AB05C433F5 for ; Thu, 31 Mar 2022 16:55:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240302AbiCaQ5R (ORCPT ); Thu, 31 Mar 2022 12:57:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36668 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233799AbiCaQ5P (ORCPT ); Thu, 31 Mar 2022 12:57:15 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3337C232126 for ; Thu, 31 Mar 2022 09:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1648745728; x=1680281728; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=IP3Qpce+WyUMM7QQju7XQB09RXxl0bxyb7Ub1Mu6XFw=; b=h8KQH+NoeIedIId8FAtpRbnODA1ENehdpJyjzsX5l8PBYUrc8wg3Y6J8 xUiJWqf1EJOq1NZtFEcMj0MyRXYfxXa21AyVEFxYk65K4B1czWauwJdNT Uh/BFFR6LXoc749hPi8il/W261YmKpQdBzHoN5H+YhT/tvSHgU+gcUR/m NClr5zWBYBVS5N3V5tITCIgPmKFDOLz5zxQIemGSy2pJFKxmXstSuHiEn NN5wX6Sf1jbAsOlEJJ2aXNejGDMYWSOZ/x9i3tPj8mJO6Xrtxgr2G/CCl W6gPY5rCmn2C8OfeJxSzS3zF/CxNot0R+Oa9SQF5FGl/COk7Gax7++ckh w==; X-IronPort-AV: E=McAfee;i="6200,9189,10302"; a="247393493" X-IronPort-AV: E=Sophos;i="5.90,225,1643702400"; d="scan'208";a="247393493" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Mar 2022 09:54:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,225,1643702400"; d="scan'208";a="522420778" Received: from lkp-server02.sh.intel.com (HELO 3231c491b0e2) ([10.239.97.151]) by orsmga006.jf.intel.com with ESMTP; 31 Mar 2022 09:54:57 -0700 Received: from kbuild by 3231c491b0e2 with local (Exim 4.95) (envelope-from ) id 1nZy4W-0000SS-Hu; Thu, 31 Mar 2022 16:54:56 +0000 Date: Fri, 1 Apr 2022 00:54:41 +0800 From: kernel test robot To: Axel Rasmussen Cc: kbuild-all@lists.01.org, Linux Memory Management List , Andrew Morton , linux-kernel@vger.kernel.org Subject: [RFC PATCH linux-next] mm/secretmem: secretmem_iops can be static Message-ID: References: <202204010033.oeIla4qb-lkp@intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <202204010033.oeIla4qb-lkp@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" mm/secretmem.c:173:31: warning: symbol 'secretmem_iops' was not declared. S= hould it be static? Fixes: 24209f2f4d62 ("mm/secretmem: fix panic when growing a memfd_secret") Reported-by: kernel test robot Signed-off-by: kernel test robot --- 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); } =20 -const struct inode_operations secretmem_iops =3D { +static const struct inode_operations secretmem_iops =3D { .setattr =3D secretmem_setattr, };