Change the type of data of ptrace::write to make it safe

[ShuiRuTian]

What does this PR do

Fix #2323

Change the signature of ptrace::write and ptrace::write_user to make them safe

Checklist:

• I have read CONTRIBUTING.md
• I have written necessary tests and rustdoc comments
• A change log has been added if this PR modifies nix's API

[ShuiRuTian]

I use the same command, but could not reproduce the issue, does anyone know the reason?

I ran cargo clippy --target x86_64-unknown-linux-gnu --all-targets --all-features -- -D warnings -A unknown-lints

[SteveLauC]

Well, it is indeed weird, I didn't reproduce it either...

Will investigate more.

[SteveLauC]

I kinda think this error is a false positive?

My guess on the reason why it is triggered is that we are directly casting a c_long to a raw pointer, but I think this is fine as the kernel won't treat it as a raw pointer but an unsigned long, so we can:

1. Allow it #[allow(clippy::not_unsafe_ptr_arg_deref)]

2. Write a comment stating why the usages of ptrace_other() within write() and write_user() are safe

   // Safety:
   

[ShuiRuTian]

Thanks for the suggestions, it's past now!

[SteveLauC]

Thanks!