Re: [PATCH 2/2] wifi: cfg80211: simplify cfg80211_mlme_register_mgmt()

On Tue, 2024-12-10 at 17:39 +0300, Dmitry Antipov wrote: > Simplify 'cfg80211_mlme_register_mgmt()' to allocate an instance of > 'struct cfg80211_mgmt_registration' only if the latter is really > needed  This part is very much broken, and I don't see that it's actually useful to add a new "goto" j

Re: [PATCH v2 1/2][next] UAPI: ethtool: Use __struct_group() in struct ethtool_link_settings

On Mon, Dec 09, 2024 at 04:39:38PM -0800, Christopher Ferris wrote: > By the way, there are some places where __struct_group is used in other > uapi headers, the only difference is that the TAG field of the macro is > left empty. That compiles fine when used in C++ code. Does this fix the C++ incl

Re: [PATCH v4 1/1] exec: seal system mappings

On Wed, Dec 11, 2024 at 2:47 PM Jeff Xu wrote: > > Hi Andrei > > Thanks for your email. > I was hoping to get some feedback from CRIU devs, and happy to see you > reaching out.. > ... > I have been thinking of other alternatives, but those would require > more understanding on CRIU use cases. > On

[PATCH] fortify: Hide run-time copy size from value range tracking

GCC performs value range tracking for variables as a way to provide better diagnostics. One place this is regularly seen is with warnings associated with bounds-checking, e.g. -Wstringop-overflow, -Wstringop-overread, -Warray-bounds, etc. In order to keep the signal-to-noise ratio high, warnings ar