mainline: stack frame size exceeds limit on allmodconfig

[musamaanjum]

The allmodconfig has been enabled recently and we have found a failed build with clang-17: https://staging.kernelci.org:9000/viewer?search=parent%3D67236768025e418acd1174cc

The logs show that build failed because of stack frame size exceeds limit 2 times.

fs/bcachefs/chardev.c:881:6: error: stack frame size (1080) exceeds limit (1024) in 'bch2_fs_ioctl' [-Werror,-Wframe-larger-than]
  881 | long bch2_fs_ioctl(struct bch_fs *c, unsigned cmd, void __user *arg)
      |      ^

drivers/net/ethernet/qlogic/qede/qede_main.c:313:6: error: stack frame size (1056) exceeds limit (1024) in 'qede_fill_by_demand_stats' [-Werror,-Wframe-larger-than]
  313 | void qede_fill_by_demand_stats(struct qede_dev *edev)
      |      ^

I've looked at allmodconfig file for this and found out that:

CONFIG_FRAME_WARN=1024

The stack frame size is quite a common warning. But as error on warning flag may be set, this warning is being treated as error. CONFIG_FRAME_WARN can be set [0 8192]. The current value is set to 1024 and errors are getting generated at 1080 and 1056. We can report this upstream and/or increase the FRAME_WARN in configurations.

cc: @crazoes @nuclearcat

[musamaanjum]

The same error is occurring again today.