[lkml]   [2006]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 0/5] lightweight robust futexes: -V1
Daniel Walker wrote:

> On Thu, 16 Feb 2006, Ingo Molnar wrote:
>> that's memory corruption - which robust futexes do not (and cannot)
>> solve. Robustness is mostly about handling sudden death (e.g. which is
>> due to oom, or is due to a user killing the task, or due to the
>> application crashing in some non-memory-corrupting way), but it cannot
>> handle all possible failure modes.
> I don't think this is a weakness in Dave or Inaky's versions. Dave
> at least maintained the bulk of the information in kernel space. The
> uaddr was used for the fast locking in userspace, but not for
> maintaining the robustness .
> Correct me if I'm wrong Dave.

In the general case of memory corruption, the data protected by the
robust futex might be corrupted, and no robust futex implementation can
protect against that, In fact it's a lot more likely since the
application code has pointers to the data but not to the robust list.

Do not meddle in the internals of kernels, for they are subtle and quick to panic.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-02-17 10:11    [W:0.030 / U:2.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site