Skip to content

tiff, bmp: return io.UnexpectedEOF on empty data #3

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

Closed
wants to merge 4 commits into from

Conversation

oneslash
Copy link
Contributor

@oneslash oneslash commented Nov 5, 2019

Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes golang/go#11391

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes and removed cla: no labels Nov 5, 2019
@gopherbot
Copy link
Contributor

This PR (HEAD: ee7b450) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 1:

(4 comments)

Hey Sardorbek,

Thank you for submitting this! Just some feedback on the commit message.

Akhil


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 772852b) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 2:

@akhil, I have edited the commit message. Thank you for the review


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 2:

Patch Set 2:

@akhil, I have edited the commit message. Thank you for the review

It appears that the commit message hasn't changed on Gerrit. Since you are
using a Pull Request, you must edit the PR’s title and description to update
the CL here. See https://github.com/golang/go/wiki/CommitMessage#github-pull-requests
for more information.

Additionally, please move the “Fixes #11391” line to the bottom of the commit
message as per the formatting guidelines.

Thanks


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes #11391
@gopherbot
Copy link
Contributor

This PR (HEAD: dc261cf) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@oneslash oneslash changed the title tiff/lzw: should return io.UnexpectedEOF on empty data tiff, bmp: return io.UnexpectedEOF on empty data Nov 6, 2019
@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 5:

Thank you, now it seems like its good


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 5: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 5:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=043ec183


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 5: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 5: -Run-TryBot Code-Review+1

Looks good.
Kindly pinging Nigel


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Nigel Tao:

Patch Set 5:

(3 comments)

Looks good. Just a couple of minor things to fix.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 19a70c0) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 6:

Thank you Nigel for review, I have done the changes.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 6:

(4 comments)

Hey Sardorbek,

It appears that Nigel's requested changes were not made in the latest patchset. I have marked them again here.

Thanks


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 6:

@akhil, I have added about nil case the test below []byte{}, do you think only nil case should stay?


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Nigel Tao:

Patch Set 6:

Patch Set 6:

@akhil, I have added about nil case the test below []byte{}, do you think only nil case should stay?

Please just have the nil case, and delete the []byte{} case.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 0e266b4) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 6:

Patch Set 6:

Patch Set 6:

@akhil, I have added about nil case the test below []byte{}, do you think only nil case should stay?

Please just have the nil case, and delete the []byte{} case.

Fixed, Nigel, thank you for the comments


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 7:

(2 comments)

Minor nitpick, thanks for working on this!


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 924636f) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/image/+/205458 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 7: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 7:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=6dae6658


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Sardorbek Pulatov:

Patch Set 7:

Akhil, removed, thank you 😊


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 8: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 8:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=90e694e4


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 8: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Akhil Indurti:

Patch Set 8: Code-Review+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/205458.
After addressing review feedback, remember to publish your drafts!

gopherbot pushed a commit that referenced this pull request Dec 6, 2019
Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes golang/go#11391

Change-Id: I73394b9dcc0d2e4e2a7bc56addb3f690791820ba
GitHub-Last-Rev: 924636f
GitHub-Pull-Request: #3
Reviewed-on: https://go-review.googlesource.com/c/image/+/205458
Run-TryBot: Akhil Indurti <aindurti@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Akhil Indurti <aindurti@gmail.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>
@gopherbot
Copy link
Contributor

This PR is being closed because golang.org/cl/205458 has been merged.

@gopherbot gopherbot closed this Dec 6, 2019
GalaxyForcew added a commit to GalaxyForcew/A1bisshy that referenced this pull request Jun 6, 2022
Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes golang/go#11391

Change-Id: I73394b9dcc0d2e4e2a7bc56addb3f690791820ba
GitHub-Last-Rev: 924636fca185e34399b558c92c1d4b80f43eadfc
GitHub-Pull-Request: golang/image#3
Reviewed-on: https://go-review.googlesource.com/c/image/+/205458
Run-TryBot: Akhil Indurti <aindurti@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Akhil Indurti <aindurti@gmail.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>
yi-ge3 added a commit to yi-ge3/wislie that referenced this pull request Jun 6, 2022
Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes golang/go#11391

Change-Id: I73394b9dcc0d2e4e2a7bc56addb3f690791820ba
GitHub-Last-Rev: 924636fca185e34399b558c92c1d4b80f43eadfc
GitHub-Pull-Request: golang/image#3
Reviewed-on: https://go-review.googlesource.com/c/image/+/205458
Run-TryBot: Akhil Indurti <aindurti@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Akhil Indurti <aindurti@gmail.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>
snapbakkhfbav added a commit to snapbakkhfbav/SayedBaladohr that referenced this pull request Oct 6, 2022
Check for an EOF when decoding the tiff and bmp headers,
so that decoding empty data does not return an EOF.

Fixes golang/go#11391

Change-Id: I73394b9dcc0d2e4e2a7bc56addb3f690791820ba
GitHub-Last-Rev: 924636fca185e34399b558c92c1d4b80f43eadfc
GitHub-Pull-Request: golang/image#3
Reviewed-on: https://go-review.googlesource.com/c/image/+/205458
Run-TryBot: Akhil Indurti <aindurti@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Akhil Indurti <aindurti@gmail.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

x/image/{tiff,bmp}: EOF instead of UnexpectedEOF
3 participants