linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Daniel, Colascione," <dancol@google.com>
Cc: kbuild-all@lists.01.org, linux-security-module@vger.kernel.org,
	James Morris <jmorris@namei.org>
Subject: [security:secure_uffd_v5.9 1/3] fs/anon_inodes.c:92:10-17: WARNING: ERR_CAST can be used with inode
Date: Thu, 4 Jun 2020 19:19:48 +0800	[thread overview]
Message-ID: <202006041944.AJeCfZpC%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git secure_uffd_v5.9
head:   d08ac70b1e0dc71ac2315007bcc3efb283b2eae4
commit: 2749d3f84a708110ed0359579be0eddd2c4036da [1/3] Add a new LSM-supporting anonymous inode interface
config: nios2-randconfig-c003-20200604 (attached as .config)
compiler: nios2-linux-gcc (GCC) 9.3.0

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


coccinelle warnings: (new ones prefixed by >>)

>> fs/anon_inodes.c:92:10-17: WARNING: ERR_CAST can be used with inode

Please review and possibly fold the followup patch.

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

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

             reply	other threads:[~2020-06-04 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 11:19 kernel test robot [this message]
2020-06-04 11:19 ` [PATCH] fix err_cast.cocci warnings kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2020-07-08  2:53 [security:secure_uffd_v5.9 1/3] fs/anon_inodes.c:92:10-17: WARNING: ERR_CAST can be used with inode kernel test robot

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=202006041944.AJeCfZpC%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dancol@google.com \
    --cc=jmorris@namei.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).