From: kbuild test robot <fengguang.wu@intel.com>
To: Andrzej Zaborowski <andrew.zaborowski@intel.com>
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [cryptodev:master 53/54] crypto/rsa-pkcs1pad.c:135:1: warning: 'pkcs1pad_encrypt_sign_complete' uses dynamic stack allocation
Date: Thu, 10 Dec 2015 02:49:27 +0800 [thread overview]
Message-ID: <201512100225.MWaG2I5C%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
head: 161151d79ff4f7ed35d4ebb0eb7727a517c34ef2
commit: 3d5b1ecdea6fb94f8c61554fcb2ba776a2d3d0e6 [53/54] crypto: rsa - RSA padding algorithm
config: s390-allmodconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 3d5b1ecdea6fb94f8c61554fcb2ba776a2d3d0e6
# save the attached .config to linux build tree
make.cross ARCH=s390
All warnings (new ones prefixed by >>):
crypto/rsa-pkcs1pad.c: In function 'pkcs1pad_encrypt_sign_complete':
>> crypto/rsa-pkcs1pad.c:135:1: warning: 'pkcs1pad_encrypt_sign_complete' uses dynamic stack allocation
}
^
vim +/pkcs1pad_encrypt_sign_complete +135 crypto/rsa-pkcs1pad.c
119 sg_nents_for_len(req->dst,
120 sizeof(zeros)),
121 zeros, sizeof(zeros));
122 }
123
124 sg_pcopy_from_buffer(req->dst,
125 sg_nents_for_len(req->dst, ctx->key_size),
126 req_ctx->out_buf, req_ctx->child_req.dst_len,
127 sizeof(zeros));
128 }
129 req->dst_len = ctx->key_size;
130
131 kfree(req_ctx->in_buf);
132 kzfree(req_ctx->out_buf);
133
134 return err;
> 135 }
136
137 static void pkcs1pad_encrypt_sign_complete_cb(
138 struct crypto_async_request *child_async_req, int err)
139 {
140 struct akcipher_request *req = child_async_req->data;
141 struct crypto_async_request async_req;
142
143 if (err == -EINPROGRESS)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 39221 bytes --]
next reply other threads:[~2015-12-09 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 18:49 kbuild test robot [this message]
2015-12-10 1:47 ` [cryptodev:master 53/54] crypto/rsa-pkcs1pad.c:135:1: warning: 'pkcs1pad_encrypt_sign_complete' uses dynamic stack allocation Herbert Xu
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=201512100225.MWaG2I5C%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=andrew.zaborowski@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@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 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.