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

[25.0 backport] builder-next: fix missing lock in ensurelayer #47527

Merged
merged 1 commit into from
Mar 7, 2024

Commits on Mar 7, 2024

  1. builder-next: fix missing lock in ensurelayer

    When this was called concurrently from the moby image
    exporter there could be a data race where a layer was
    written to the refs map when it was already there.
    
    In that case the reference count got mixed up and on
    release only one of these layers was actually released.
    
    Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
    (cherry picked from commit 37545cc)
    Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
    tonistiigi authored and vvoland committed Mar 7, 2024
    Configuration menu
    Copy the full SHA
    d250e13 View commit details
    Browse the repository at this point in the history