#315 closed bug (fixed)
device read/writes don't lock memory — at Version 5
Reported by: | axeld | Owned by: | nobody |
---|---|---|---|
Priority: | critical | Milestone: | R1/beta2 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | diver | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
BeOS made sure the memory buffer passed to a device read/write was safe to be written to. Haiku currently requires the drivers to use user_memcpy() to access those buffers, which is not compatible to how the old driver interface works.
Also, the new file system interface doesn't solve this issue yet, either...
Change History (5)
comment:1 by , 19 years ago
Cc: | added |
---|
comment:2 by , 10 years ago
Platform: | → All |
---|---|
Version: | → R1/Development |
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 6 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Now the use of user_memcpy is mandatory thanks to SMAP, and all drivers have been converted to use it. Closing as fixed.
Note:
See TracTickets
for help on using tickets.
Still an issue?