Skip to content

Conversation

TomSweeneyRedHat
Copy link
Member

… targets

When examining a file that we're adding to an archive to see if it's hard linked to another file that's already been written, or to one that might be written later, only set an entry in the inode->name map that points to the entry we're writing for the first file. This keeps us from writing tar headers with Typeflag==TypeLink and a Linkname that points to another entry with Typeflag==TypeLink in cases where the inode has more than two names.

Addresses: containers/buildah#6297 for the release-1.59 branch and eventualy Buildah v1.41.* and Podman v5.6.*

Cherry-pick of #2357

… targets

When examining a file that we're adding to an archive to see if it's
hard linked to another file that's already been written, or to one that
might be written later, only set an entry in the inode->name map that
points to the entry we're writing for the first file.  This keeps us
from writing tar headers with Typeflag==TypeLink and a Linkname that
points to another entry with Typeflag==TypeLink in cases where the inode
has more than two names.

Addresses: containers/buildah#6297 for the
release-1.59 branch and eventualy Buildah v1.41.* and Podman v5.6.*

Cherry-pick of containers#2357

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
@TomSweeneyRedHat
Copy link
Member Author

@nalind @mtrmac PTAL. This looked like the only candidate PR to pick back into c/storage 1.59 from main. Holler if you disagree.

@nalind
Copy link
Member

nalind commented Jul 31, 2025

Yes, this is the one that was foremost in my mind.
Try the bot's cherry picking command next time, it might save you some work.

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this one.

LGTM.

@nalind
Copy link
Member

nalind commented Jul 31, 2025

/approve
/lgtm

Copy link
Contributor

openshift-ci bot commented Jul 31, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nalind, TomSweeneyRedHat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit ad6f4c9 into containers:release-1.59 Jul 31, 2025
20 checks passed
@TomSweeneyRedHat
Copy link
Member Author

@nalind, I'm a bit of a Luddite and have had very mixed experiences with the cherry-pick-bot. I generally prefer doing it by hand, even when I misstep like I did this time.

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