Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1667385

Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM

From kbuild test robot <lkp@intel.com>
Newsgroups linux.kernel
Subject Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM
Date 2017-06-16 04:30 +0200
Message-ID <tSPbk-2nO-5@gated-at.bofh.it> (permalink)
References <tPWCl-7iA-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Matt,

[auto build test WARNING on security/next]
[also build test WARNING on v4.12-rc5 next-20170615]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Matt-Brown/Add-Trusted-Path-Execution-as-a-stackable-LSM/20170609-115004
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> security/tpe/tpe_lsm.c:45:5: sparse: symbol 'print_tpe_error' was not declared. Should it be static?
>> security/tpe/tpe_lsm.c:128:5: sparse: symbol 'tpe_mmap_file' was not declared. Should it be static?
>> security/tpe/tpe_lsm.c:137:5: sparse: symbol 'tpe_file_mprotect' was not declared. Should it be static?
>> security/tpe/tpe_lsm.c:160:17: sparse: symbol 'tpe_sysctl_path' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v2 1/1]  Add Trusted Path Execution as a stackable LSM Matt Brown <matt@nmatt.com> - 2017-06-08 05:50 +0200
  Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Kees Cook <keescook@chromium.org> - 2017-06-09 04:40 +0200
    Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Matt Brown <matt@nmatt.com> - 2017-06-09 06:00 +0200
      Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Mimi Zohar <zohar@linux.vnet.ibm.com> - 2017-06-09 12:20 +0200
        Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Kees Cook <keescook@chromium.org> - 2017-06-09 15:00 +0200
          Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Matt Brown <matt@nmatt.com> - 2017-06-09 15:20 +0200
          Re: [kernel-hardening] Re: [PATCH v2 1/1] Add Trusted Path Execution  as a stackable LSM Matt Brown <matt@nmatt.com> - 2017-06-09 15:20 +0200
            Re: [kernel-hardening] Re: [PATCH v2 1/1] Add Trusted Path  Execution as a stackable LSM Mimi Zohar <zohar@linux.vnet.ibm.com> - 2017-06-09 15:50 +0200
          Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM Mimi Zohar <zohar@linux.vnet.ibm.com> - 2017-06-09 15:20 +0200
  Re: [PATCH v2 1/1] Add Trusted Path Execution as a stackable LSM kbuild test robot <lkp@intel.com> - 2017-06-16 04:30 +0200
  [RFC PATCH] print_tpe_error() can be static kbuild test robot <lkp@intel.com> - 2017-06-16 04:30 +0200

csiph-web