-
Notifications
You must be signed in to change notification settings - Fork 15
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
error: write on a pipe with no reader #1651
Comments
UNIX03 conformance requires utilities to flush stdout before exiting and raise an error if writing fails. Flushing already happens on a call to exit and thus automatically on a return from main. Write failure is then detected by LLVM's default SIGPIPE handler. The handler already exits with a non-zero code, but conformance additionally requires an error message.
Does |
It appears this is related to |
I cannot reproduce this outside of the build system unfortunately :( running the commands that I see directly above the message when running with |
Can you share some of those commands? |
Sure; pardon the formatting dump:
I did notice more errors with a higher level of parallelism with |
So this appears to be related to how the kernel calls |
Perhaps redirecting stderr of $(OBJDUMP) to /dev/null is the solution when piping the output to |
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: Fiqri Ardyansyah <fiqri0927936@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: Arindam Bhattacharjee <abhattacharjee717@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: Fiqri Ardyansyah <fiqri0927936@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Change-Id: 8503b19b17e629cd29c74b96b4016388af66e392 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: TogoFire <italomellopereira@gmail.com> (cherry picked from commit 99cc51b70fb4c8be3b6f15aaee4f18fa39087f09)
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: Fiqri Ardyansyah <fiqri0927936@gmail.com> Signed-off-by: rezaadi0105 <rezaadipangestu5@gmail.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: Fiqri Ardyansyah <fiqri0927936@gmail.com> Signed-off-by: rezaadi0105 <rezaadipangestu5@gmail.com>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
fixes ClangBuiltLinux/linux#1651 Signed-off-by: engstk <eng.stk@sapo.pt>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
- This suppresses following errors for us: error: write on a pipe with no reader - Fix references are from issue ClangBuiltLinux/linux#1651 Co-authored-by: GhostMaster69-dev <rathore6375@gmail.com> Signed-off-by: GhostMaster69-dev <rathore6375@gmail.com> [Diaz1401: also apply on cmd_modversions_S] Signed-off-by: Diaz1401 <reagor8161@outlook.com>
After llvm/llvm-project@51b557a, I am seeing that error messages in several of my builds. It appears to be more pronounced on stable trees vs. mainline and -next.
On 5.18, I can reproduce it with:
The text was updated successfully, but these errors were encountered: