On Thu, Jan 09, 2025 at 01:35:30PM +0100, Pablo Neira Ayuso wrote: > According to 0708a0afe291 ("mm: Consider __GFP_NOWARN flag for oversized > kvmalloc() calls"), use INT_MAX as maximum size for the conntrack > hashtable. Otherwise, it is possible to hit WARN_ON_ONCE in > __kvmalloc_node_noprof() when __GFP_NOWARN flag is unset when resizing. > > Note: hashtable resize is only possible from init_netns. Please, ignore this duplicated patch with incorrect [nf] tag that slipped through this submission. Sorry for the inconvenience. Thanks.