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 a panic when a tag value was empty #5370

Merged
merged 1 commit into from
Jan 18, 2016

Conversation

jsternberg
Copy link
Contributor

A panic would happen if you wrote the following:
cpu,host=

There was a missing bounds check when scanning the tag value.

Fixes #5262.

@jsternberg jsternberg force-pushed the js-5262-panic-on-empty-tag-value branch from 5790af9 to 690df18 Compare January 15, 2016 22:11
@jwilder
Copy link
Contributor

jwilder commented Jan 15, 2016

👍

@jsternberg jsternberg force-pushed the js-5262-panic-on-empty-tag-value branch from 690df18 to 7b7db6e Compare January 15, 2016 22:22
A panic would happen if you wrote the following:
    cpu,host=

There was a missing bounds check when scanning the tag value.

Fixes #5262.
@jsternberg jsternberg force-pushed the js-5262-panic-on-empty-tag-value branch from 7b7db6e to 8eac790 Compare January 16, 2016 17:21
jsternberg added a commit that referenced this pull request Jan 18, 2016
…alue

Fix a panic when a tag value was empty
@jsternberg jsternberg merged commit 0e0f85a into master Jan 18, 2016
@jsternberg jsternberg deleted the js-5262-panic-on-empty-tag-value branch January 18, 2016 14:27
@e-dard
Copy link
Contributor

e-dard commented Jan 19, 2016

When I wrote this scanTagsValue I didn't expect the first byte to be out of bounds. I think I made an error elsewhere to end up in that function. I will take a look at why this happened at some point!

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.

3 participants