Skip to content

fix: missing read-write flag in reopenFDOnError#95

Merged
ldez merged 2 commits intogofrs:mainfrom
crazy-max:fix-resetfd
Jul 22, 2024
Merged

fix: missing read-write flag in reopenFDOnError#95
ldez merged 2 commits intogofrs:mainfrom
crazy-max:fix-resetfd

Conversation

@crazy-max
Copy link
Contributor

relates to docker/buildx#2593

seems a regression introduced in b659e1e that removes read-write flag: b659e1e#diff-87c2c4fe0fb43f4b38b4bee45c1b54cfb694c61e311f93b369caa44f6c1323ffR192

cc @ldez

@ldez ldez self-requested a review July 22, 2024 18:30
@ldez
Copy link
Contributor

ldez commented Jul 22, 2024

🤔 technically the retry should use the same flag as the setFh, so, for me, the previous behavior has a problem.

@ldez
Copy link
Contributor

ldez commented Jul 22, 2024

I think I understand now, it's inspired by util-linux: it's not a "classic" retry but a specific case retry.

@ldez ldez marked this pull request as ready for review July 22, 2024 20:12
@ldez ldez changed the title fix missing read-write flag in reopenFDOnError fix: missing read-write flag in reopenFDOnError Jul 22, 2024
@ldez ldez added the bug label Jul 22, 2024
Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

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

LGTM

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.

2 participants