Re: Using map_user_kiobuf()

> Am I the only one who finds the READ/WRITE option back to front? > > No, I was just thinking it should be change to USER_READ, USER_WRITE > or something a little more obvious. Eh, read data from userspace and write data to userspace? Oops. FROM_USER TO_USER - To unsubscribe from thi

RE: Using map_user_kiobuf()

ther by a module or > a user programme, a kiobuf seemed a good way of representing it. A layer > converts user memory to a kiobuf using map_user_kiobuf(). There are a number of fixes pending for 2.4, and released for 2.2, but nothing that would explain the sort of kernel corruption you are r

Re: Using map_user_kiobuf()

a module or > a user programme, a kiobuf seemed a good way of representing it. A layer > converts user memory to a kiobuf using map_user_kiobuf(). There are a number of fixes pending for 2.4, and released for 2.2, but nothing that would explain the sort of kernel corruption you are reportin

Using map_user_kiobuf()

layer converts user memory to a kiobuf using map_user_kiobuf(). To test if it would work, I wrote a short test that passed 1,000,000 bytes of memory to a module that wrote a pattern into the memory. The pattern was checked in the user programme to ensure it worked. The test does work in so much