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

rgw: don't use s->bucket for metadata api path entry #7408

Merged
merged 1 commit into from
Feb 15, 2016
Merged

Conversation

yehudasa
Copy link
Member

Fixes #14549

s->bucket is only initialized at the object store handler (post auth
callback). We don't want to initialize it for other cases because
it's not a real bucket, and initializing it will require going through
the authorization path for this 'bucket'.

Signed-off-by: Yehuda Sadeh yehuda@redhat.com

Fixes #14549

s->bucket is only initialized at the object store handler (post auth
callback). We don't want to initialize it for other cases because
it's not a real bucket, and initializing it will require going through
the authorization path for this 'bucket'.

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
@zaitcev
Copy link
Contributor

zaitcev commented Jan 30, 2016

I think "going through the authorization path" is nice enough. How about this:
https://gist.github.com/zaitcev/2980329845d2da4bcf38
?

@yehudasa
Copy link
Member Author

@zaitcev the problem there is that we end up keeping s->bucket_name for something that is not a bucket, so it doesn't really make anything better. Also, it's a fix for only this specific op, not a generic fix. I'd rather have something more generic (e.g., setting some other field on the req_state). I think that for now my fix is good enough.

oritwas added a commit that referenced this pull request Feb 15, 2016
rgw: don't use s->bucket for metadata api path entry

Reviewed-by: Orit Wasserman <owasserm@redhat.com>
@oritwas oritwas merged commit bdb035c into master Feb 15, 2016
@liewegas liewegas deleted the wip-14549 branch November 23, 2016 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants