Skip to content
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

Fix leak for symbolic link in exfat_lookup #100

Merged
merged 1 commit into from Jan 3, 2017

Conversation

cccheng
Copy link

@cccheng cccheng commented Dec 22, 2016

While exfat_lookup() for symbolic file, we Should not alloc memory
to EXFAT_I(inode)->target since the corredspoding exfat inode info
is still is in memory and EXFAT_I(inode)->target has not released
yet. If we do so, memory leak would happen. Therefore we only alloc
it if not null.

Reviewed-by: Ethan Wu ethanwu@synology.com
Signed-off-by: Chung-Chiang Cheng cccheng@synology.com

While exfat_lookup() for symbolic file, we Should not alloc memory
to EXFAT_I(inode)->target since the corredspoding exfat inode info
is still is in memory and EXFAT_I(inode)->target has not released
yet. If we do so, memory leak would happen. Therefore we only alloc
it if not null.

Reviewed-by: Ethan Wu <ethanwu@synology.com>
Signed-off-by: Chung-Chiang Cheng <cccheng@synology.com>
@dorimanx dorimanx merged commit 22910c9 into dorimanx:master Jan 3, 2017
@cccheng cccheng deleted the Slink_leak branch January 24, 2017 15:54
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.

None yet

2 participants