From: kernel test robot <lkp@intel.com>
To: Adrian Ratiu <adrian.ratiu@collabora.com>, linux-fsdevel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-doc@vger.kernel.org, kernel@collabora.com, gbiv@google.com,
ryanbeltran@google.com, inglorion@google.com,
ajordanr@google.com, jorgelo@chromium.org,
Adrian Ratiu <adrian.ratiu@collabora.com>,
Jann Horn <jannh@google.com>, Kees Cook <keescook@chromium.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v4 1/2] proc: pass file instead of inode to proc_mem_open
Date: Sat, 25 May 2024 05:05:28 +0800 [thread overview]
Message-ID: <202405250413.EENbErWw-lkp@intel.com> (raw)
In-Reply-To: <20240524192858.3206-1-adrian.ratiu@collabora.com>
Hi Adrian,
kernel test robot noticed the following build errors:
[auto build test ERROR on kees/for-next/pstore]
[also build test ERROR on kees/for-next/kspp linus/master v6.9 next-20240523]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Adrian-Ratiu/proc-restrict-proc-pid-mem/20240525-033201
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
patch link: https://lore.kernel.org/r/20240524192858.3206-1-adrian.ratiu%40collabora.com
patch subject: [PATCH v4 1/2] proc: pass file instead of inode to proc_mem_open
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20240525/202405250413.EENbErWw-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 7aa382fd7257d9bd4f7fc50bb7078a3c26a1628c)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240525/202405250413.EENbErWw-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/202405250413.EENbErWw-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/proc/task_nommu.c:3:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> fs/proc/task_nommu.c:262:27: error: incompatible pointer types passing 'struct inode *' to parameter of type 'struct file *' [-Werror,-Wincompatible-pointer-types]
262 | priv->mm = proc_mem_open(inode, PTRACE_MODE_READ);
| ^~~~~
fs/proc/internal.h:298:46: note: passing argument to parameter 'file' here
298 | struct mm_struct *proc_mem_open(struct file *file, unsigned int mode);
| ^
1 warning and 1 error generated.
vim +262 fs/proc/task_nommu.c
b76437579d1344 Siddhesh Poyarekar 2012-03-21 251
b76437579d1344 Siddhesh Poyarekar 2012-03-21 252 static int maps_open(struct inode *inode, struct file *file,
b76437579d1344 Siddhesh Poyarekar 2012-03-21 253 const struct seq_operations *ops)
662795deb854b3 Eric W. Biederman 2006-06-26 254 {
dbf8685c8e2140 David Howells 2006-09-27 255 struct proc_maps_private *priv;
dbf8685c8e2140 David Howells 2006-09-27 256
27692cd56e2aa6 Oleg Nesterov 2014-10-09 257 priv = __seq_open_private(file, ops, sizeof(*priv));
ce34fddb5bafb4 Oleg Nesterov 2014-10-09 258 if (!priv)
ce34fddb5bafb4 Oleg Nesterov 2014-10-09 259 return -ENOMEM;
ce34fddb5bafb4 Oleg Nesterov 2014-10-09 260
2c03376d2db005 Oleg Nesterov 2014-10-09 261 priv->inode = inode;
27692cd56e2aa6 Oleg Nesterov 2014-10-09 @262 priv->mm = proc_mem_open(inode, PTRACE_MODE_READ);
27692cd56e2aa6 Oleg Nesterov 2014-10-09 263 if (IS_ERR(priv->mm)) {
27692cd56e2aa6 Oleg Nesterov 2014-10-09 264 int err = PTR_ERR(priv->mm);
27692cd56e2aa6 Oleg Nesterov 2014-10-09 265
27692cd56e2aa6 Oleg Nesterov 2014-10-09 266 seq_release_private(inode, file);
27692cd56e2aa6 Oleg Nesterov 2014-10-09 267 return err;
27692cd56e2aa6 Oleg Nesterov 2014-10-09 268 }
27692cd56e2aa6 Oleg Nesterov 2014-10-09 269
ce34fddb5bafb4 Oleg Nesterov 2014-10-09 270 return 0;
662795deb854b3 Eric W. Biederman 2006-06-26 271 }
662795deb854b3 Eric W. Biederman 2006-06-26 272
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-24 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 19:28 [PATCH v4 1/2] proc: pass file instead of inode to proc_mem_open Adrian Ratiu
2024-05-24 19:28 ` [PATCH v4 2/2] proc: restrict /proc/pid/mem Adrian Ratiu
2024-05-25 5:49 ` Randy Dunlap
2024-05-27 11:21 ` Adrian Ratiu
2024-05-31 21:29 ` Kees Cook
2024-05-24 21:05 ` kernel test robot [this message]
2024-05-24 21:56 ` [PATCH v4 1/2] proc: pass file instead of inode to proc_mem_open kernel test robot
2024-05-31 21:14 ` Kees Cook
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=202405250413.EENbErWw-lkp@intel.com \
--to=lkp@intel.com \
--cc=adrian.ratiu@collabora.com \
--cc=ajordanr@google.com \
--cc=brauner@kernel.org \
--cc=gbiv@google.com \
--cc=inglorion@google.com \
--cc=jannh@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryanbeltran@google.com \
/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.