2,257
edits
Changes
Jump to navigation
Jump to search
Line 57:
Line 57: + +
+ unhashed sockets task
|-
|-
| crtools || file locks || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?
| crtools || file locks || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?
|-
| kernel || unhashed sockets || - || When we create a tcp socket it doesn't get to eny hashes and is not reported by diag infra. However, there exists stuff that we can configure on such a socket and there's no existing APIs for getting this info (e.g. -- bind to device). What to do? Report unhashed sockets with diag or extend API for this crap?
|}
|}