tun: Some bits required for tun's checkpoint-restore (v2)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | tun: Add ability to create tun device with given indexdrivers/ include/ | +21 | 0 replies | |
| 2/4 | tun: Report whether the queue is attached or notdrivers/ | +3 | 0 replies | |
| 3/4 | tun: Allow to skip filter on attachdrivers/ include/ | +8 | 0 replies | |
| 4/4 | tun: Get skfilter layoutdrivers/ include/ | +11 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH net-next 0/4] tun: Some bits required for tun's checkpoint-restore (v2)
Hi,
After taking a closer look on tun checkpoint-restore I've found several issues with the tun's API that make it impossible to dump and restore the state of tun device and attached tun-files.
The proposed API changes are all about extending the existing ioctl-based stuff. Patches fit today's net-next.
This v2 has David's comments about patch #1 fixed. All the rest is the same.
Signed-off-by Pavel Emelyanov <[email protected]>