> This patch handle potential null pointer dereference in > 'raw3270_setup_device()', When 'raw3270_setup_console()' fails to > allocate memory for 'rp' or 'ascebc'. 1. Can a wording approach (like the following) be a better change description? A null pointer is stored in a local variable after a call of the function “kzalloc” failed. This pointer was passed to a subsequent call of the function “raw3270_setup_device” where an undesirable dereference will be performed then. Thus add corresponding return value checks. 2. Would you like to add any tags (like “Fixes”) accordingly? 3. The allocated two memory areas are immediately overwritten by the called function. Can zero-initialisation be omitted by calling the function “kmalloc” instead? 4. Under which circumstances will development interests grow for increasing the application of scope-based resource management? https://elixir.bootlin.com/linux/v6.10-rc4/source/include/linux/cleanup.h#L8 Regards, Markus
