make vmsplice unsafe#2777
Conversation
19f9721 to
eb540be
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
e0b2a0e to
7aae780
Compare
I'm hesitant to use "fixed" for breaking change. |
10defca to
b712ba2
Compare
|
Can we just remove this function? |
|
is this ready for review? |
|
I still don't like current unsafe doc. |
asomers
left a comment
There was a problem hiding this comment.
This is a definite improvement. But it's still way to unsafe for any but the bravest and most performance-obsessed programmer to use. It's beyond the scope of this PR, but I wonder if a safe Rust API could be devised? Something like make vmsplice only accept pointers to memory allocated by a special allocator, and only accept them by move, not by borrow.
|
Someone said RAM allocated by mmap can is bit safer. |
|
I'm not familiar with kernel. But how about input ->(sendfile etc...) memfd ->(mmap, edit and sendfile) -> output |
Co-authored-by: xtqqczze <45661989+xtqqczze@users.noreply.github.com>
What does this PR do
make vmsplice unsafe. Closes #2633
Checklist:
CONTRIBUTING.md