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

Jump to bottom

x/sys/unix: solaris EventPort panic when processing events after Close #54363

Closed
nshalman opened this issue Aug 10, 2022 · 2 comments
Closed

x/sys/unix: solaris EventPort panic when processing events after Close #54363

nshalman opened this issue Aug 10, 2022 · 2 comments
Assignees
@nshalman
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@nshalman
Copy link

While stress testing fsnotify/fsnotify#371 I ran into a panic that I tracked down to
one thread calling Close() while another thread was still trying to process one or more events
it had already gotten back from the OS.

A CR will follow shortly.
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Aug 10, 2022
@gopherbot gopherbot added this to the Unreleased milestone Aug 10, 2022
@gopherbot
Copy link

Change https://go.dev/cl/422338 mentions this issue: unix: Fix EventPort panic after Close

@thanm thanm added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 10, 2022
@nshalman
Copy link
Author

@mknyszek you can assign this one to me as well.

nshalman added a commit to nshalman/sys that referenced this issue Aug 17, 2022
@nshalman
unix: fix event port panic after close
ffe4817 
Fixes golang/go#54363

Change-Id: I38813aefaf58ef91605e0a6e3e6622c8a39d6a8d
@nshalman nshalman mentioned this issue Aug 25, 2022
Closed
@nshalman nshalman mentioned this issue Sep 8, 2022
Merged
@golang golang locked and limited conversation to collaborators Sep 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@nshalman nshalman

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@nshalman @gopherbot @thanm