Change config flag on BlueField branch

[Dimitri John Ledkov]

Hi,

On Fri, Jun 11, 2021 at 6:33 AM Moshe Shemesh <moshe at nvidia.com> wrote:
>
> Hello Jesse,
>
> I am contacting you as I am not sure what is the policy for setting required config flag on Ubuntu kernel BlueField branch for a functionality which should run on it.
> As part of development of functionality to protect the server from SYN attack on BlueField kernel, we need to set the following config flag: CONFIG_NF_CONNTRACK=y.
> This is essential for this new functionality which as a fire wall should be on by default.
> I would like to know this change is applicable.
>

If any config is a module, and yet it is / will be always loaded, it
is usually reasonable to change it from =m to =y. There are a few
config changes from =m to =y in the bluefield kernel already. So this
is not unprecedented. [1]

Please open a bug report and if possible send a patch to change the
config option. E.g.
https://lists.ubuntu.com/archives/kernel-team/2021-May/119892.html

[1] $ python3 ./scripts/diffconfig
debian.master/config/config.common.ubuntu
debian.bluefield/config/config.common.ubuntu | grep 'm -> y' | wc -l
172

Regards,

Dimitri.