From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/2] tee: add AMD-TEE driver
Date: Fri, 25 Oct 2019 16:13:27 +0800 [thread overview]
Message-ID: <201910251646.hIniTXGs%lkp@intel.com> (raw)
In-Reply-To: <fd7b187b01cccd690dc3c71d6c5f2520bb9e303a.1571818136.git.Rijo-john.Thomas@amd.com>
[-- Attachment #1: Type: text/plain, Size: 3254 bytes --]
Hi Rijo-john",
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc4 next-20191024]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Thomas-Rijo-john/TEE-driver-for-AMD-APUs/20191025-081700
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 39a38bcba4ab6e5285b07675b0e42c96eec35e67
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers//tee/amdtee/shm_pool.c: In function 'amdtee_config_shm':
>> drivers//tee/amdtee/shm_pool.c:128:2: warning: 'dmabuf_mgr' may be used uninitialized in this function [-Wmaybe-uninitialized]
kfree(dmabuf_mgr);
^~~~~~~~~~~~~~~~~
>> drivers//tee/amdtee/shm_pool.c:127:2: warning: 'priv_mgr' may be used uninitialized in this function [-Wmaybe-uninitialized]
kfree(priv_mgr);
^~~~~~~~~~~~~~~
vim +/dmabuf_mgr +128 drivers//tee/amdtee/shm_pool.c
77
78 struct tee_shm_pool *amdtee_config_shm(void)
79 {
80 struct tee_shm_pool *pool = NULL;
81 struct tee_shm_pool_mgr *priv_mgr;
82 struct tee_shm_pool_mgr *dmabuf_mgr;
83 int ret;
84
85 pool = kzalloc(sizeof(*pool), GFP_KERNEL);
86 if (!pool) {
87 ret = -ENOMEM;
88 goto err;
89 }
90
91 priv_mgr = kzalloc(sizeof(*priv_mgr), GFP_KERNEL);
92 if (!priv_mgr) {
93 ret = -ENOMEM;
94 goto err;
95 }
96
97 dmabuf_mgr = kzalloc(sizeof(*dmabuf_mgr), GFP_KERNEL);
98 if (!dmabuf_mgr) {
99 ret = -ENOMEM;
100 goto err;
101 }
102
103 pool->private_mgr = priv_mgr;
104 pool->dma_buf_mgr = dmabuf_mgr;
105 /*
106 * Initialize memory manager for driver private shared memory
107 */
108 ret = pool_mem_mgr_init(pool->private_mgr, 3 /* 8 byte aligned */);
109 if (ret)
110 goto err;
111
112 /*
113 * Initialize memory manager for dma_buf shared memory
114 */
115 ret = pool_mem_mgr_init(pool->dma_buf_mgr, PAGE_SHIFT);
116 if (ret)
117 goto err;
118
119 return pool;
120 err:
121 if (ret == -ENOMEM)
122 pr_err("%s: failed to configure shared memory pool\n",
123 __func__);
124 if (pool && pool->private_mgr->private_data)
125 kfree(pool->private_mgr->private_data);
126 kfree(pool);
> 127 kfree(priv_mgr);
> 128 kfree(dmabuf_mgr);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70234 bytes --]
next prev parent reply other threads:[~2019-10-25 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 11:30 [RFC PATCH 0/2] TEE driver for AMD APUs Thomas, Rijo-john
2019-10-23 11:30 ` [RFC PATCH 1/2] tee: allow compilation of tee subsystem for AMD CPUs Thomas, Rijo-john
2019-10-23 11:31 ` [RFC PATCH 2/2] tee: add AMD-TEE driver Thomas, Rijo-john
2019-10-25 8:13 ` kbuild test robot [this message]
2019-10-25 21:02 ` kbuild test robot
2019-10-25 21:02 ` [RFC PATCH] tee: shmctx can be static kbuild test robot
2019-11-05 15:28 ` [RFC PATCH 2/2] tee: add AMD-TEE driver Jens Wiklander
2019-11-26 13:01 ` Thomas, Rijo-john
2019-11-05 15:17 ` [RFC PATCH 0/2] TEE driver for AMD APUs Jens Wiklander
2019-11-26 13:00 ` Thomas, Rijo-john
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=201910251646.hIniTXGs%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.