client: use null snapc to check pool permission #6497
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
snap inodes' ->snaprealm can be NULL, so dereferencing it in check_pool_perm() can cause segment fault. The pool permission check does not write any data, so it's safe to use null snapc. Fixes: ceph#13714 Signed-off-by: Yan, Zheng <zyan@redhat.com>
jcsp
added a commit
that referenced
this pull request
Nov 9, 2015
client: use null snapc to check pool permission Reviewed-by: John Spray <john.spray@redhat.com>
ghost
added
the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
snap inodes' ->snaprealm can be NULL, so dereferencing it in
check_pool_perm() can cause segment fault. The pool permission
check does not write any data, so it's safe to use null snapc.
Fixes: #13714
Signed-off-by: Yan, Zheng zyan@redhat.com