mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Jason A. Donenfeld" <zx2c4@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/net/wireguard/allowedips.c:59:1: warning: the frame size of 1040 bytes is larger than 1024 bytes
Date: Mon, 10 Feb 2020 12:59:40 +0800	[thread overview]
Message-ID: <202002101239.lVITTq0Y%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9
commit: e7096c131e5161fa3b8e52a650d7719d2857adfd net: WireGuard secure network tunnel
date:   9 weeks ago
config: x86_64-lck-7890 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
        git checkout e7096c131e5161fa3b8e52a650d7719d2857adfd
        # 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>

All warnings (new ones prefixed by >>):

   drivers/net/wireguard/allowedips.c: In function 'root_free_rcu':
>> drivers/net/wireguard/allowedips.c:59:1: warning: the frame size of 1040 bytes is larger than 1024 bytes [-Wframe-larger-than=]
    }
    ^
   drivers/net/wireguard/allowedips.c: In function 'root_remove_peer_lists':
   drivers/net/wireguard/allowedips.c:72:1: warning: the frame size of 1040 bytes is larger than 1024 bytes [-Wframe-larger-than=]
    }
    ^
   drivers/net/wireguard/allowedips.c: In function 'walk_remove_by_peer.isra.3':
   drivers/net/wireguard/allowedips.c:126:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
    }
    ^

vim +59 drivers/net/wireguard/allowedips.c

    47	
    48	static void root_free_rcu(struct rcu_head *rcu)
    49	{
    50		struct allowedips_node *node, *stack[128] = {
    51			container_of(rcu, struct allowedips_node, rcu) };
    52		unsigned int len = 1;
    53	
    54		while (len > 0 && (node = stack[--len])) {
    55			push_rcu(stack, node->bit[0], &len);
    56			push_rcu(stack, node->bit[1], &len);
    57			kfree(node);
    58		}
  > 59	}
    60	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49624 bytes --]

                 reply	other threads:[~2020-02-10  5:01 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=202002101239.lVITTq0Y%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zx2c4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®