[lkml]   [2006]   [Feb]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 0/5] lightweight robust futexes: -V1
On Wednesday 15 February 2006 20:49, Christopher Friesen wrote:

> The goal is for the kernel to unlock the mutex, but the next task to
> aquire it gets some special notification that the status is unknown. At
> that point the task can either validate/clean up the data and reset the
> mutex to clean (if it can) or it can give up the mutex and pass it on to
> some other task that does know how to validate/clean up.

The "send signal when any mapper dies" proposal would do that. The other process
could catch the signal and do something with it.

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-15 21:04    [W:0.055 / U:0.836 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site