-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New found memleak in zpl_mount #5490
Labels
Component: Memory Management
kernel memory management
Milestone
Comments
The issue here appears to be if |
11 tasks
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
zfs_sb_create would normally takes ownership of zmo, and it will be freed in zfs_sb_free. However, when zfs_sb_create fails we need to explicit free it. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes openzfs#5490 Closes openzfs#5496
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
zfs_sb_create would normally takes ownership of zmo, and it will be freed in zfs_sb_free. However, when zfs_sb_create fails we need to explicit free it. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes openzfs#5490 Closes openzfs#5496 Requires-builders: style
behlendorf
pushed a commit
that referenced
this issue
Feb 3, 2017
zfs_sb_create would normally takes ownership of zmo, and it will be freed in zfs_sb_free. However, when zfs_sb_create fails we need to explicit free it. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes #5490 Closes #5496
wli5
pushed a commit
to wli5/zfs
that referenced
this issue
Feb 28, 2017
zfs_sb_create would normally takes ownership of zmo, and it will be freed in zfs_sb_free. However, when zfs_sb_create fails we need to explicit free it. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes openzfs#5490 Closes openzfs#5496
wli5
pushed a commit
to wli5/zfs
that referenced
this issue
Feb 28, 2017
zfs_sb_create would normally takes ownership of zmo, and it will be freed in zfs_sb_free. However, when zfs_sb_create fails we need to explicit free it. Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes openzfs#5490 Closes openzfs#5496
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http://build.zfsonlinux.org/builders/Ubuntu%2016.04%20x86_64%20Kmemleak%20%28TEST%29/builds/15/steps/shell_11/logs/kmemleak
The text was updated successfully, but these errors were encountered: