From: kbuild test robot <fengguang.wu@intel.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 9864/10975] crypto/twofish_common.c:700:1: warning: the frame size of 4800 bytes is larger than 2048 bytes
Date: Thu, 14 Jan 2016 14:58:27 +0800 [thread overview]
Message-ID: <201601141423.wlAnUxhW%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2874 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bf976ab690dea9d0ee260fc8881fef511a0e3566
commit: 1b15c325c3def847397c1badc5dbe5914efc8d7e [9864/10975] UBSAN: run-time undefined behavior sanity checker
config: x86_64-randconfig-x001-01140840 (attached as .config)
reproduce:
git checkout 1b15c325c3def847397c1badc5dbe5914efc8d7e
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
crypto/twofish_common.c: In function '__twofish_setkey':
>> crypto/twofish_common.c:700:1: warning: the frame size of 4800 bytes is larger than 2048 bytes [-Wframe-larger-than=]
}
^
vim +700 crypto/twofish_common.c
2729bb42 Joachim Fritschi 2006-06-20 684 } else { /* 128-bit key */
2729bb42 Joachim Fritschi 2006-06-20 685 /* Compute the S-boxes. */
2729bb42 Joachim Fritschi 2006-06-20 686 for ( i = j = 0, k = 1; i < 256; i++, j += 2, k += 2 ) {
2729bb42 Joachim Fritschi 2006-06-20 687 CALC_SB_2( i, calc_sb_tbl[j], calc_sb_tbl[k] );
2729bb42 Joachim Fritschi 2006-06-20 688 }
2729bb42 Joachim Fritschi 2006-06-20 689
e2b21b50 Denys Vlasenko 2007-10-26 690 /* Calculate whitening and round subkeys */
e2b21b50 Denys Vlasenko 2007-10-26 691 for ( i = 0; i < 8; i += 2 ) {
e2b21b50 Denys Vlasenko 2007-10-26 692 CALC_K (w, i, q0[i], q1[i], q0[i+1], q1[i+1]);
e2b21b50 Denys Vlasenko 2007-10-26 693 }
e2b21b50 Denys Vlasenko 2007-10-26 694 for ( i = 0; i < 32; i += 2 ) {
e2b21b50 Denys Vlasenko 2007-10-26 695 CALC_K (k, i, q0[i+8], q1[i+8], q0[i+9], q1[i+9]);
e2b21b50 Denys Vlasenko 2007-10-26 696 }
2729bb42 Joachim Fritschi 2006-06-20 697 }
2729bb42 Joachim Fritschi 2006-06-20 698
2729bb42 Joachim Fritschi 2006-06-20 699 return 0;
2729bb42 Joachim Fritschi 2006-06-20 @700 }
81559f9a Jussi Kivilinna 2011-10-18 701 EXPORT_SYMBOL_GPL(__twofish_setkey);
2729bb42 Joachim Fritschi 2006-06-20 702
81559f9a Jussi Kivilinna 2011-10-18 703 int twofish_setkey(struct crypto_tfm *tfm, const u8 *key, unsigned int key_len)
81559f9a Jussi Kivilinna 2011-10-18 704 {
81559f9a Jussi Kivilinna 2011-10-18 705 return __twofish_setkey(crypto_tfm_ctx(tfm), key, key_len,
81559f9a Jussi Kivilinna 2011-10-18 706 &tfm->crt_flags);
81559f9a Jussi Kivilinna 2011-10-18 707 }
2729bb42 Joachim Fritschi 2006-06-20 708 EXPORT_SYMBOL_GPL(twofish_setkey);
:::::: The code at line 700 was first introduced by commit
:::::: 2729bb427f686e47970406d6bde6b11892885f29 [CRYPTO] twofish: Split out common c code
:::::: TO: Joachim Fritschi <jfritschi@freenet.de>
:::::: CC: Herbert Xu <herbert@gondor.apana.org.au>
---
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: 21693 bytes --]
reply other threads:[~2016-01-14 6:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201601141423.wlAnUxhW%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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