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

x/sys/unix, windows: needs to track update to syscall #10150

Closed
robpike opened this issue Mar 12, 2015 · 18 comments
Closed

x/sys/unix, windows: needs to track update to syscall #10150

robpike opened this issue Mar 12, 2015 · 18 comments

Comments

@robpike
Copy link
Contributor

robpike commented Mar 12, 2015

Since 1.4, my hand scan of the changes to the core repo's syscall package yields these CLs, many of which need to be applied to the go.sys repo:

https://go-review.googlesource.com/#/c/1372/
https://go-review.googlesource.com/#/c/1640/
https://go-review.googlesource.com/#/c/1930/
https://go-review.googlesource.com/#/c/1932/
https://go-review.googlesource.com/#/c/1940/
https://go-review.googlesource.com/#/c/2123/
https://go-review.googlesource.com/#/c/2307/
https://go-review.googlesource.com/#/c/2589/
https://go-review.googlesource.com/#/c/2746/
https://go-review.googlesource.com/#/c/2810/
https://go-review.googlesource.com/#/c/2815/
https://go-review.googlesource.com/#/c/2816/
https://go-review.googlesource.com/#/c/2817/
https://go-review.googlesource.com/#/c/3014/
https://go-review.googlesource.com/#/c/3983/
https://go-review.googlesource.com/#/c/4164/
https://go-review.googlesource.com/#/c/4330/
https://go-review.googlesource.com/#/c/5005/
https://go-review.googlesource.com/#/c/5287/
https://go-review.googlesource.com/#/c/5288/
https://go-review.googlesource.com/#/c/5576/
https://go-review.googlesource.com/#/c/5833/
https://go-review.googlesource.com/#/c/5835/
https://go-review.googlesource.com/#/c/5836/
https://go-review.googlesource.com/#/c/5837/
https://go-review.googlesource.com/#/c/6350/
https://go-review.googlesource.com/#/c/6372/
https://go-review.googlesource.com/#/c/6385/
https://go-review.googlesource.com/#/c/6391/
https://go-review.googlesource.com/#/c/7123/

This is not a perfect list. Some may be missing and some are internal/syscall and might not apply.

These CLs (and whatever follow, which should be added to this bug) need to be examined and, if appropriated, adapted and applied to go.sys.

More fundamentally, we also need to stop these packages from diverging so much in future. Some process may be required to encourage updating.

From a higher perspective, I am surprised at the amount of churn in a supposedly quiet package.

@robpike robpike added this to the Go1.5 milestone Mar 12, 2015
@robpike robpike self-assigned this Mar 12, 2015
@robpike
Copy link
Contributor Author

robpike commented Mar 12, 2015

cc @davecheney @adg

@alexbrainman
Copy link
Member

I looked at windows related syscall package changes only. I can see 3.

syscall: use go generate to build zsyscall_windows.go
https://go-review.googlesource.com/#/c/1940/

I have (had for a while ready for review) correspondent go.sys change
windows: use go generate to build zsyscall_windows.go
https://go-review.googlesource.com/#/c/2530/
If someone wants to review it, go ahead.

syscall: Readlink doesn't handle junction on windows
https://go-review.googlesource.com/#/c/2307/

I dropped ball with this change. I will take care of it.

syscall: make mksyscall_windows.go to work even when output does not uses unsafe
https://go-review.googlesource.com/#/c/5005/

This change does not need to be copied to go.sys. Only z*.go go.sys files needs to be re-generated. That has already happened in unrelated go.sys change.

Alex

@mikioh
Copy link
Contributor

mikioh commented Mar 13, 2015

I would propose to remove networking-related stuff from sys/unix; specifically the following:

  1. Subset of routing message parsers for BSD variants
  2. Subset of netlink message parsers for Linux
  3. BPF (Berkeley Packet Filter) for BSD variants
  4. LSF (Linux Socket Filter) for Linux

Simply net sub repository seems to be right place for them. Thoughts?

@robpike
Copy link
Contributor Author

robpike commented Mar 13, 2015

Mikioh: I don't know enough about networking to guarantee whether this is OK, but that sounds reasonable to me.

Alex: 2530 LGTM. Thanks.

@mikioh mikioh changed the title go.sys: needs to track update to syscall unix, windows: needs to track update to syscall Mar 14, 2015
@robpike
Copy link
Contributor Author

robpike commented Mar 14, 2015

@robpike
Copy link
Contributor Author

robpike commented Mar 15, 2015

https://go-review.googlesource.com/#/c/4913/ also needs to be applied

@robpike
Copy link
Contributor Author

robpike commented Mar 15, 2015

https://go-review.googlesource.com/7543 also needs to be applied

gopherbot pushed a commit to golang/sys that referenced this issue Mar 20, 2015
Those libraries, routing message parsers, netlink message parsers,
berkeley packat filter are linux packet filter, are subsets and just for
the net package of standard library. It would be better keeping,
extending them at the net sub repository instead of here.

Updates golang/go#10150.

Change-Id: I1ca437bea2e2be7f7f8f6496d4db291629f49136
Reviewed-on: https://go-review.googlesource.com/7581
Reviewed-by: Russ Cox <rsc@golang.org>
Reviewed-by: Rob Pike <r@golang.org>
@4ad
Copy link
Member

4ad commented Mar 24, 2015

https://go-review.googlesource.com/8022/ also needs to be applied.

gopherbot pushed a commit to golang/sys that referenced this issue Mar 24, 2015
Some Linux architectures (e.g. arm64) don't have the getpgrp syscall,
use getpgid(0) to emulate it.

Update golang/go#10150.

This brings CL 8022 that has been applied to the syscall package to
x/sys.

Change-Id: I24c6d7e8b5b2f075ca4e68b142b2e03ab8a43342
Signed-off-by: Shenghou Ma <minux@golang.org>
Reviewed-on: https://go-review.googlesource.com/8023
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@robpike
Copy link
Contributor Author

robpike commented Mar 24, 2015

@robpike
Copy link
Contributor Author

robpike commented Mar 26, 2015

@robpike
Copy link
Contributor Author

robpike commented Apr 9, 2015

@robpike
Copy link
Contributor Author

robpike commented Apr 9, 2015

https://go-review.googlesource.com/#/c/8721/ handles 6350 and 6385

@robpike
Copy link
Contributor Author

robpike commented Apr 9, 2015

gopherbot pushed a commit to golang/sys that referenced this issue Apr 10, 2015
Related issue golang/go#10150

Change-Id: I38e3e13238624655bb828d501bc865ff8a4312e9
Reviewed-on: https://go-review.googlesource.com/7493
Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
@rsc rsc changed the title unix, windows: needs to track update to syscall x/sys/unix, windows: needs to track update to syscall Apr 14, 2015
@rsc rsc modified the milestones: Unreleased, Go1.5 Apr 14, 2015
@rsc rsc removed the repo-sys label Apr 14, 2015
@robpike
Copy link
Contributor Author

robpike commented May 13, 2015

@bradfitz
Copy link
Contributor

This style of bug is hard to follow or close.

N smaller, closable bugs might be better.

@robpike
Copy link
Contributor Author

robpike commented May 13, 2015

I like having it in one.

http://golang.org/cl/8723
fixed by
https://go-review.googlesource.com/10035

@4ad
Copy link
Member

4ad commented May 13, 2015

Perhaps a milestone? Whatever github has to group issues.

ianlancetaylor added a commit to golang/sys that referenced this issue May 13, 2015
This is a copy of http://golang.org/cl/9870 in the syscall package.

This is in preparation for arm64 support, as the arm64 Linux kernel
does not have an inotify_init system call, only inotify_init1.

Update golang/go#10150.

Change-Id: I9224a094af79adbb2f5714ad977b195d5a941eb0
Reviewed-on: https://go-review.googlesource.com/10036
Reviewed-by: Rob Pike <r@golang.org>
@robpike
Copy link
Contributor Author

robpike commented May 13, 2015

https://golang.org/cl/9870/
fixed by
https://go-review.googlesource.com/#/c/10036/

I will create a new bug with only the remaining ones, since people seem offended by this particular noise source when there is so much other noise out there.

@robpike robpike closed this as completed May 13, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
@rsc rsc unassigned robpike Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants