Re: [meta][dunfell][PATCH] libinput: Add fix for CVE-2022-1215

["Ranjitsinh Rathod" <ranjitsinhrathod1991@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

Hi Steve,

It seems something is wrong with this patch and also in the patching tool within Yocto as well.

When I apply this patch, it is getting applied cleanly, without any warnings and/or patch-fuzz, which means the source code should reflect as per the patch.
But when I go to the source code on the path "build/tmp/work/<architecture>/libinput/1.15.2-r0/libinput-1.15.2" and see the file "src/evdev.c", it seems below two Hunk's are not getting reflected.

@@ -2469,7 +2478,7 @@ evdev_device_get_output(struct evdev_device *device)
const char *
evdev_device_get_sysname(struct evdev_device *device)
{
- return udev_device_get_sysname(device->udev_device);
+ return device->sysname;
}

const char *
@@ -3066,6 +3075,8 @@ evdev_device_destroy(struct evdev_device *device)
if (device->base.group)
libinput_device_group_unref(device->base.group);

+ free(device->log_prefix_name);
+ free(device->sysname);
free(device->output_name);
filter_destroy(device->pointer.filter);
libinput_timer_destroy(&device->scroll.timer);

Can you please check this from your end too? If this is the case, there is a serious issue where patching is failing silently which needs attention.

As I have seen the patch in the testing branch "http://cgit.openembedded.org/openembedded-core-contrib/commit/?h=stable/dunfell-nut&id=6a31bfaee4d715f31e69cea1eed05484d9d7a999" I considered to post this email as it seems you also did not get any warnings/error during the patching and even compilation.

Thanks,
Ranjitsinh Rathod

[-- Attachment #2: Type: text/html, Size: 2260 bytes --]