Messages in this thread | | | Date | Tue, 15 Nov 2005 12:08:50 +1100 | From | Peter Chubb <> | Subject | Re: [PATCH] getrusage sucks |
| |
>>>>> "Claudio" == Claudio Scordino <cloud.of.andor@gmail.com> writes:
>> You need to wrap this with a read_lock(&tasklist_lock) to be safe, >> I think. Claudio> Right. Probably this was the meaning also of Hua's Claudio> mail. Sorry, but I didn't get it immediately.
Claudio> So, what if I do as follows ? Do you see any problem with Claudio> this solution ?
You should probably restrict the ability to read a process's usage to a suitably privileged user -- i.e., effective uid same as the task's, or capable(CAP_SYS_RESOURCE) or maybe capable(CAP_SYS_ADMIN)
-- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever* - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |