Messages in this thread | | | Date | Tue, 21 Nov 2023 14:03:15 +0100 | From | David Sterba <> | Subject | Re: [PATCH v2] btrfs: ref-verify: fix memory leaks |
| |
On Sat, Nov 18, 2023 at 02:40:12PM +0530, Bragatheswaran Manickavel wrote: > In btrfs_ref_tree_mod(), when !parent 're' was allocated > through kmalloc(). In the following code, if an error occurs, > the execution will be redirected to 'out' or 'out_unlock' and > the function will be exited. However, on some of the paths, > 're' are not deallocated and may lead to memory leaks. > > For example : lookup_block_entry() for 'be' returns null, the > out label will be invoked. During that flow ref and ra was > freed but not re, which can potentially lead to memleak > > Reported-and-tested-by: syzbot+d66de4cbf532749df35f@syzkaller.appspotmail.com > Closes: https://syzkaller.appspot.com/bug?extid=d66de4cbf532749df35f > Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
Added to misc-next, thanks.
| |