Reviewed by: Serapheim Dimitropoulos <[email protected]> Reviewed by: Sara Hartse <[email protected]> Reviewed by: Pavel Zakharov <[email protected]> Reviewed by: Matt Ahrens <[email protected]>
after running "zfstest" and then using "reboot -d" and "::findleaks", there's a couple of leaks like the following: kmem_alloc_8 leak: 2 buffers, 8 bytes each, 16 bytes total ADDR BUFADDR TIMESTAMP THREAD CACHE LASTLOG CONTENTS ffffff071a067978 ffffff071a0416c0 9b097add290 ffffff002126fc40 ffffff06e1628888 ffffff06f0e0b440 ffffff06f7592ea0 kmem_cache_alloc_debug+0x2e0 kmem_cache_alloc+0xdd kmem_alloc+0x4b ddi_strdup+0x5f strdup+0x13 get_receive_resume_stats_impl+0x31c get_special_prop+0x192 zcp_get_system_prop+0x79 zcp_get_prop+0xab luaD_precall+0x1fd luaV_execute+0x355 luaD_call+0x88 f_call+0x1d luaD_rawrunprotected+0x69 luaD_pcall+0x55 Upstream bug: DLPX-47891 You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/667 -- Commit Summary -- * 8601 memory leak in get_special_prop() -- File Changes -- M usr/src/uts/common/fs/zfs/zcp_get.c (17) -- Patch Links -- https://github.com/openzfs/openzfs/pull/667.patch https://github.com/openzfs/openzfs/pull/667.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/667 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/T0f24bab931612c63-M9ed763583a08277154dfdee1 Delivery options: https://openzfs.topicbox.com/groups/developer/subscription
