Skip to content

Conversation

mtkaczyk
Copy link
Member

According to manual:
On success, udev_monitor_receive_device() returns a pointer to a newly referenced device that was received via the monitor. The caller is responsible to drop this reference when done.

Fixes:#195

@mtkaczyk mtkaczyk force-pushed the fix_udev_memleak branch 2 times, most recently from b4271f3 to bc9c33f Compare October 6, 2025 09:26
@mtkaczyk mtkaczyk force-pushed the fix_udev_memleak branch 2 times, most recently from c93f752 to 3399d84 Compare October 7, 2025 05:46
Copy link
Contributor

@mwilck mwilck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for your patience!

According to manual:
On success, udev_monitor_receive_device() returns a pointer to a newly
referenced device that was received via the monitor. The caller is
responsible to drop this reference when done.

Signed-off-by: Mariusz Tkaczyk <[email protected]>
@mtkaczyk
Copy link
Member Author

@XiaoNi87 please take a look :)

Copy link
Collaborator

@XiaoNi87 XiaoNi87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Mariusz

Thanks for the patch. Looks good to me.

@mtkaczyk mtkaczyk merged commit d478aff into md-raid-utilities:main Oct 14, 2025
9 checks passed
@mtkaczyk mtkaczyk deleted the fix_udev_memleak branch October 14, 2025 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants