of: dynamic: Synchronize of_changeset_destroy() with the devlink removals

Linux kernel 安全漏洞

将以下内容从英文翻译成中文： 关于：动态：将changeset_destroy()的同步与devlink移除操作对齐

In the Linux kernel, the following vulnerability has been resolved: of: dynamic: Synchronize of_changeset_destroy() with the devlink removals In the following sequence: 1) of_platform_depopulate() 2) of_overlay_remove() During the step 1, devices are destroyed and devlinks are removed. During the step 2, OF nodes are destroyed but __of_changeset_entry_destroy() can raise warnings related to missing of_node_put(): ERROR: memory leak, expected refcount 1 instead of 2 ... Indeed, during the devlink removals performed at step 1, the removal itself releasing the device (and the attached of_node) is done by a job queued in a workqueue and so, it is done asynchronously with respect to function calls. When the warning is present, of_node_put() will be called but wrongly too late from the workqueue job. In order to be sure that any ongoing devlink removals are done before the of_node destruction, synchronize the of_changeset_destroy() with the devlink removals.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于内存泄漏。

在Linux内核中，已解决了以下漏洞： of：动态：在设备链接移除时同步 of_changeset_destroy() 函数 在以下序列中： 1）of_platform_depopulate() 2）of_overlay_remove() 在步骤1中，设备被销毁，设备链接移除。 在步骤2中，OF节点被销毁，但 __of_changeset_entry_destroy() 可以抛出与缺少 of_node_put() 相关的警告： 错误：内存泄漏，期望的引用计数为1，而不是2...... 确实，在步骤1中执行的设备链接移除后，释放设备（以及附加的 of_node）由一个队列在工作队列中完成，因此相对于函数调用，它是异步的。 当出现警告时，将调用of_node_put()，但错误地太晚来自工作队列任务。 为了确保在of_node销毁之前完成任何正在进行的设备链接移除，需要在设备链接移除与of_changeset_destroy()函数之间同步。