On 2024/1/2 16:51, Markus Elfring wrote:
…
A few update suggestions were taken into account
from static source code analysis.
…
Return directly after a failed kzalloc() in smc_fill_gid_list()
Improve exception handling in smc_llc_cli_add_link_invite()
net/smc/af_smc.c | 2 +-
net/smc/smc_llc.c | 15 +++++++--------
2 files changed, 8 insertions(+), 9 deletions(-)
…
I see you want to fix the kfree(NULL) issues in these two patches.
I propose to avoid redundant function calls at various source code places.
But I am wondering if this is necessary, since kfree() can handle NULL correctly.
Would you prefer only required data processing in affected function implementations?
Thank you Markus. I understood that you want to avoid redundant function calls.
But it is not very attractive to me since the calls occur on low-frequency paths
or unlikely condition, resulting in limited performance loss and the current
kfree() usage is fine and common. So what is the benfit?
I noticed that some other discussions are on-going. It seems like you are trying
to change other similiar places. Let's collect more opinions.
https://lore.kernel.org/netdev/828bb442-29d0-4bb8-b90d-f200bdd4faf6@xxxxxx/
https://lore.kernel.org/netdev/90679f69-951c-47b3-b86f-75fd9fde3da3@xxxxxx/
https://lore.kernel.org/netdev/dc0a1c9d-ceca-473d-9ad5-89b59e6af2e7@xxxxxx/
https://lore.kernel.org/netdev/cde82080-c715-473c-97ac-6ef66bba6d64@xxxxxx/
Thanks.
Regards,
Markus
