From: Catalin Marinas > Sent: 28 June 2018 15:49 ... > > > > Mmmm yes. > > I tend to favor a sort of opposite approach. When we have an address > > that must not be dereferenced as-such (and sometimes when the address > > can be from both __user & __kernel space) I prefer to use a ulong > > which will force the use of the required operation before being > > able to do any sort of dereferencing and this won't need horrible > > casts with __force (it, of course, all depends on the full context). > > I agree. That's what the kernel uses in functions like get_user_pages() > which take ulong as an argument. Similarly mmap() and friends don't > expect the pointer to be dereferenced, hence the ulong argument. The > interesting part that the man page (and the C library header > declaration) shows such address argument as void *. We could add a > syscall wrapper in the arch code, only that it doesn't feel consistent > with the "rule" that ulong addresses are not actually tagged pointers. For most modern calling conventions it would make sense to put 'user' addresses (and physical ones from that matter) into a structure. That way you get much stronger typing from C itself. The patch would, of course, be huge! David -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
