On Fri, 30 May 2008, Arjan van de Ven wrote:
> Rank 4: task_has_capability (warning)
> Reported 181 times (202 total reports)
> [out of tree] Bug in the proprietary firegl driver
> warning only shows up in tainted kernels
> This warning was last seen in version 2.6.25.3, and first seen in
> 2.6.25.
> More info:
> http://www.kerneloops.org/searchweek.php?search=task_has_capability
This is a shining example of why people should avoid binary drivers. I'd
guess that the bug is related to the new 64-bit capability code.
It'd be really interesting to know what this driver is doing with
capabilities in the first place.
If anyone is using this driver, the output of the following command as a
non-root user from gnome-terminal or similar may be of interest:
$ cat /proc/self/status |grep ^Cap
It should generally be all zeroes.
- James
--
James Morris
<[email protected]>
James Morris wrote:
> On Fri, 30 May 2008, Arjan van de Ven wrote:
>
>> Rank 4: task_has_capability (warning)
>> Reported 181 times (202 total reports)
>> [out of tree] Bug in the proprietary firegl driver
>> warning only shows up in tainted kernels
>> This warning was last seen in version 2.6.25.3, and first seen in
>> 2.6.25.
>> More info:
>> http://www.kerneloops.org/searchweek.php?search=task_has_capability
>
> This is a shining example of why people should avoid binary drivers. I'd
> guess that the bug is related to the new 64-bit capability code.
>
> It'd be really interesting to know what this driver is doing with
> capabilities in the first place.
it's easy; it's making the user root via the following function:
void ATI_API_CALL KCL_PosixSecurityCapSetEffectiveVector(KCL_TYPE_Cap cap)
{
capt_t(current->cap_effective) = cap;
}