golang
unix/linux: update to Linux kernel 6.4
This PR (HEAD: 4b796d506f4fa0085d95990e220142a6402480f5) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/521157.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to register for Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Gopher Robot:
Patch Set 1:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Hi.
This PR adds F_SEAL_EXEC, which is used to forbid future modifications of a file exec bit.
It was first added in kernel 6.3 1.
On a general way, do you think it could be possible to add a CI job reading kernel include/uapi/linux files to check if all the flags have a golang counterpart?
Best regards.
Message from t hepudds:
Patch Set 2:
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from t hepudds:
Patch Set 3:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 3:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from Francis Laniel:
Patch Set 3:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
This PR (HEAD: c9d6602dfea1b0d0eb50a0587d08f268ec6c963e) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/521157.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to register for Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Francis Laniel:
Patch Set 5:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 5:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from Francis Laniel:
Patch Set 5:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!
Message from Francis Laniel:
Patch Set 5:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/521157. After addressing review feedback, remember to publish your drafts!