All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:untested.securityfs 6/8] security/integrity/ima/ima_fs.c:524:27: error: 'ima_policy' undeclared; did you mean 'vma_policy'?
Date: Fri, 9 May 2025 17:11:12 +0100	[thread overview]
Message-ID: <20250509161112.GW2023217@ZenIV> (raw)
In-Reply-To: <202505092310.0UXOhVZP-lkp@intel.com>

On Fri, May 09, 2025 at 11:47:36PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git untested.securityfs
> head:   b0b8e25f92ec20e266859de5f823b4e39b8e2f9d
> commit: 08433f2507554980bc891d8b17c1968c81cb144b [6/8] ima_fs: don't bother with removal of files in directory we'll be removing
> config: i386-buildonly-randconfig-006-20250509 (https://download.01.org/0day-ci/archive/20250509/202505092310.0UXOhVZP-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505092310.0UXOhVZP-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202505092310.0UXOhVZP-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    security/integrity/ima/ima_fs.c: In function 'ima_release_policy':
> >> security/integrity/ima/ima_fs.c:524:27: error: 'ima_policy' undeclared (first use in this function); did you mean 'vma_policy'?
>      524 |         securityfs_remove(ima_policy);
>          |                           ^~~~~~~~~~
>          |                           vma_policy
>    security/integrity/ima/ima_fs.c:524:27: note: each undeclared identifier is reported only once for each function it appears in

	Yeah, that line also needs to be removed - it's handled by
securityfs_remove(ima_dir); a few lines later.

      reply	other threads:[~2025-05-09 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 15:47 [viro-vfs:untested.securityfs 6/8] security/integrity/ima/ima_fs.c:524:27: error: 'ima_policy' undeclared; did you mean 'vma_policy'? kernel test robot
2025-05-09 16:11 ` Al Viro [this message]

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=20250509161112.GW2023217@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@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.