public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Vlad Buslov <vladbu@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Sasha Levin <sashal@kernel.org>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [stable:linux-5.4.y 3300/8640] net/sched/cls_flower.c:296:12: warning: stack frame size (1040) exceeds limit (1024) in 'fl_classify'
Date: Mon, 5 Jun 2023 17:38:00 +0200	[thread overview]
Message-ID: <2023060543-unhelpful-reclining-63af@gregkh> (raw)
In-Reply-To: <20230605153209.GA2480995@dev-arch.thelio-3990X>

On Mon, Jun 05, 2023 at 08:32:09AM -0700, Nathan Chancellor wrote:
> On Mon, Jun 05, 2023 at 03:11:24PM +0300, Vlad Buslov wrote:
> > On Mon 05 Jun 2023 at 18:59, kernel test robot <lkp@intel.com> wrote:
> > > Hi Vlad,
> > >
> > > First bad commit (maybe != root cause):
> > >
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.4.y
> > > head:   cf0b1e5482eaeb4db15c9e703267483dba88b575
> > > commit: 5f2e54391893c67b709a64b280417ca0318adb73 [3300/8640] net/sched: flower: fix parsing of ethertype following VLAN header
> > > config: mips-randconfig-r013-20230605 (https://download.01.org/0day-ci/archive/20230605/202306051816.mO3hqt7d-lkp@intel.com/config)
> > > compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 4faf3aaf28226a4e950c103a14f6fc1d1fdabb1b)
> > > reproduce (this is a W=1 build):
> > >         mkdir -p ~/bin
> > >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > >         chmod +x ~/bin/make.cross
> > >         # install mips cross compiling tool for clang build
> > >         # apt-get install binutils-mipsel-linux-gnu
> > >         # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=5f2e54391893c67b709a64b280417ca0318adb73
> > >         git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > >         git fetch --no-tags stable linux-5.4.y
> > >         git checkout 5f2e54391893c67b709a64b280417ca0318adb73
> > >         # save the config file
> > >         mkdir build_dir && cp config build_dir/.config
> > >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=mips olddefconfig
> > >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash net/sched/
> > >
> > > If you fix the issue, kindly add following tag where applicable
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202306051816.mO3hqt7d-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>):
> > >
> > >>> net/sched/cls_flower.c:296:12: warning: stack frame size (1040) exceeds limit (1024) in 'fl_classify' [-Wframe-larger-than]
> > >    static int fl_classify(struct sk_buff *skb, const struct tcf_proto *tp,
> > >               ^
> > >    1 warning generated.
> > >
> > >
> > > vim +/fl_classify +296 net/sched/cls_flower.c
> > >
> > > e0ace68af2acfe Paul Blakey            2019-07-09  295  
> > > 77b9900ef53ae0 Jiri Pirko             2015-05-12 @296  static int fl_classify(struct sk_buff *skb, const struct tcf_proto *tp,
> > > 77b9900ef53ae0 Jiri Pirko             2015-05-12  297  		       struct tcf_result *res)
> > > 77b9900ef53ae0 Jiri Pirko             2015-05-12  298  {
> > > 77b9900ef53ae0 Jiri Pirko             2015-05-12  299  	struct cls_fl_head *head = rcu_dereference_bh(tp->root);
> > > 77b9900ef53ae0 Jiri Pirko             2015-05-12  300  	struct fl_flow_key skb_mkey;
> > 
> > The stack usage of fl_classify() has already been addressed in later
> > kernels by commit 0af413bd3e2d ("flow_dissector: work around stack frame
> > size warning") which moved mkey into fl_mask_lookup(). Not sure what
> > else can be done since my commit just adds a new flow dissector fields
> > that are needed to correctly parse packets with multiple VLAN headers.
> 
> 0af413bd3e2d seems like a reasonable cherry-pick for linux-5.4.y to me
> if the warning is showing up there, which seems like the only thing that
> needs to be done for this report.

That sounds good to me, now picked!

greg k-h

      reply	other threads:[~2023-06-05 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 10:59 [stable:linux-5.4.y 3300/8640] net/sched/cls_flower.c:296:12: warning: stack frame size (1040) exceeds limit (1024) in 'fl_classify' kernel test robot
2023-06-05 12:11 ` Vlad Buslov
2023-06-05 15:32   ` Nathan Chancellor
2023-06-05 15:38     ` Greg Kroah-Hartman [this message]

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=2023060543-unhelpful-reclining-63af@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jiri@nvidia.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=vladbu@nvidia.com \
    /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