All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v4 3/3] prctl: Allow ptrace capable processes to change /proc/self/exe
Date: Wed, 01 Jul 2020 16:19:10 +0800	[thread overview]
Message-ID: <202007011644.gndDDCMi%lkp@intel.com> (raw)
In-Reply-To: <20200701064906.323185-4-areber@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 8257 bytes --]

Hi Adrian,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on pcmoore-selinux/next]
[also build test ERROR on kselftest/next linus/master v5.8-rc3 next-20200701]
[cannot apply to security/next-testing]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Adrian-Reber/capabilities-Introduce-CAP_CHECKPOINT_RESTORE/20200701-145119
base:   https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
config: i386-tinyconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   make[2]: *** No rule to make target 'fs//fs_parser.o', needed by 'fs//built-in.a'.
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/file-mmu.c:29:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/file-mmu.o] Error 1
   In file included from fs//attr.c:17:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/inode.c:33:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[2]: *** [scripts/Makefile.build:281: fs//xattr.o] Error 1
   cc1: some warnings being treated as errors
   make[2]: *** [scripts/Makefile.build:497: fs//ramfs] Error 2
   make[2]: Target '__build' not remade because of errors.
   make[1]: *** [Makefile:1764: fs/] Error 2
   make[1]: Target '__all' not remade because of errors.
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/inode.o] Error 1
   make[3]: Target '__build' not remade because of errors.
--
   make[2]: *** No rule to make target 'fs//fs_parser.o', needed by 'fs//built-in.a'.
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/file-mmu.c:29:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/file-mmu.o] Error 1
   In file included from fs//attr.c:17:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/inode.c:33:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[2]: *** [scripts/Makefile.build:281: fs//xattr.o] Error 1
   cc1: some warnings being treated as errors
   make[2]: *** [scripts/Makefile.build:497: fs//ramfs] Error 2
   make[2]: Target '__build' not remade because of errors.
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/inode.o] Error 1
   make[3]: Target '__build' not remade because of errors.
--
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/file-mmu.c:29:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/file-mmu.o] Error 1
   In file included from include/linux/fs_context.h:14,
                    from include/linux/fs_parser.h:11,
                    from include/linux/ramfs.h:5,
                    from fs//ramfs/inode.c:33:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors
   make[3]: *** [scripts/Makefile.build:281: fs//ramfs/inode.o] Error 1
   make[3]: Target '__build' not remade because of errors.
--
   In file included from fs//attr.c:17:
   include/linux/security.h: In function 'security_prctl_set_mm_exe_file':
>> include/linux/security.h:1130:9: error: implicit declaration of function 'cap_prctl_set_mm_exe_file'; did you mean 'security_prctl_set_mm_exe_file'? [-Werror=implicit-function-declaration]
    1130 |  return cap_prctl_set_mm_exe_file(exe_file);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~
         |         security_prctl_set_mm_exe_file
   cc1: some warnings being treated as errors

vim +1130 include/linux/security.h

  1127	
  1128	static inline int security_prctl_set_mm_exe_file(struct file *exe_file)
  1129	{
> 1130		return cap_prctl_set_mm_exe_file(exe_file);
  1131	}
  1132	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 7287 bytes --]

  reply	other threads:[~2020-07-01  8:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01  6:49 [PATCH v4 0/3] capabilities: Introduce CAP_CHECKPOINT_RESTORE Adrian Reber
2020-07-01  6:49 ` [PATCH v4 1/3] " Adrian Reber
2020-07-01  8:27   ` Christian Brauner
2020-07-03 11:11     ` Adrian Reber
2020-07-01  6:49 ` [PATCH v4 2/3] selftests: add clone3() CAP_CHECKPOINT_RESTORE test Adrian Reber
2020-07-02 20:53   ` Serge E. Hallyn
2020-07-03 11:18     ` Adrian Reber
2020-07-03 18:12       ` Serge E. Hallyn
2020-07-01  6:49 ` [PATCH v4 3/3] prctl: Allow ptrace capable processes to change /proc/self/exe Adrian Reber
2020-07-01  8:19   ` kernel test robot [this message]
2020-07-01  8:55   ` Christian Brauner
2020-07-02 21:58     ` Serge E. Hallyn
2020-07-01 22:25   ` kernel test robot
2020-07-02 21:16   ` Serge E. Hallyn
2020-07-02 22:00     ` Paul Moore
2020-07-06 17:13       ` Nicolas Viennot
2020-07-06 17:44         ` Christian Brauner
2020-07-07 15:45           ` Christian Brauner
2020-07-07 20:27             ` Cyrill Gorcunov

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=202007011644.gndDDCMi%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.