From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 1/5] fs/proc: Introduce /proc/all/stat
Date: Tue, 11 Aug 2020 02:21:07 +0800 [thread overview]
Message-ID: <202008110219.QkNFHT3R%lkp@intel.com> (raw)
In-Reply-To: <20200810145852.9330-2-elubarsky.linux@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Hi Eugene,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on v5.8 next-20200810]
[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]
url: https://github.com/0day-ci/linux/commits/Eugene-Lubarsky/Introduce-proc-all-to-gather-stats-from-all-processes/20200810-230035
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git fc80c51fd4b23ec007e88d4c688f2cac1b8648e7
config: x86_64-randconfig-m001-20200810 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
fs/proc/base.c:3876 proc_all_stop() warn: inconsistent indenting
vim +3876 fs/proc/base.c
3866
3867 static void proc_all_stop(struct seq_file *m, void *v)
3868 {
3869 if (v) {
3870 struct all_iter *iter = (struct all_iter *) v;
3871 struct task_struct *task = iter->tgid_iter.task;
3872
3873 if (task)
3874 put_task_struct(task);
3875
> 3876 kfree(v);
3877 }
3878 }
3879
---
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: 37286 bytes --]
next prev parent reply other threads:[~2020-08-10 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:58 [RFC PATCH 0/5] Introduce /proc/all/ to gather stats from all processes Eugene Lubarsky
2020-08-10 14:58 ` [RFC PATCH 1/5] fs/proc: Introduce /proc/all/stat Eugene Lubarsky
2020-08-10 18:21 ` kernel test robot [this message]
2020-08-10 14:58 ` [RFC PATCH 2/5] fs/proc: Introduce /proc/all/statm Eugene Lubarsky
2020-08-10 14:58 ` [RFC PATCH 3/5] fs/proc: Introduce /proc/all/status Eugene Lubarsky
2020-08-10 14:58 ` [RFC PATCH 4/5] fs/proc: Introduce /proc/all/io Eugene Lubarsky
2020-08-10 14:58 ` [RFC PATCH 5/5] fs/proc: Introduce /proc/all/statx Eugene Lubarsky
2020-08-10 15:04 ` [RFC PATCH 0/5] Introduce /proc/all/ to gather stats from all processes Greg KH
2020-08-10 15:27 ` Eugene Lubarsky
2020-08-10 15:41 ` Greg KH
2020-08-25 9:59 ` Eugene Lubarsky
2020-08-12 7:51 ` Andrei Vagin
2020-08-13 4:47 ` David Ahern
2020-08-13 8:03 ` Andrei Vagin
2020-08-13 15:01 ` Eugene Lubarsky
2020-08-20 17:41 ` Andrei Vagin
2020-08-25 10:00 ` Eugene Lubarsky
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=202008110219.QkNFHT3R%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.