Messages in this thread | | | Date | Wed, 18 Jan 2012 04:23:24 -0500 | From | KOSAKI Motohiro <> | Subject | Re: [RFC] syscalls, x86: Add __NR_kcmp syscall |
| |
(1/18/12 4:19 AM), Pavel Emelyanov wrote: >> I think Eric only said gt/lt compare is useful. We don't need to expose bare >> pointer order. example, kcmp(rotate(ptr, per-task-random-value)) is enough >> hide the critical information. I think. > > The per-task might break thinks up in case > > (tsk1->file != tsk2->file)&& (rotate(tsk1->file, tsk1->random) == rotate(tsk2->file, tsk2->rotate))
I meant,
(tsk1->file != tsk2->file) && (rotate(tsk1->file, caller_task->random) == rotate(tsk2->file, caller_task->random))
> > but I agree, that the overall idea of comparing not bare pointers, but those poisoned with > some global value can address the Peter's concerns about rootkits.
| |