Re: [RFC] syscalls, x86: Add __NR_kcmp syscall

[KOSAKI Motohiro]

(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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/