On Mon, 2003-05-19 at 15:37, Peter T. Breuer wrote:
> "David Woodhouse wrote:"
> > To be honest, if any programmer is capable of committing this error and
> > not finding and fixing it for themselves, then they're also capable, and
> > arguably _likely_, to introduce subtle lock ordering discrepancies which
> > will cause deadlock once in a blue moon.
> >
> > I don't _want_ you to make life easier for this hypothetical programmer.
> >
> > I want them to either learn to comprehend locking _properly_, or take up
> > gardening instead.
>
> Let's quote the example from rubini & corbet of the sbull block device
> driver. The request function ends like so:
defective locking in a driver is no excuse to pamper over it with
recusrive shite.
This archive was generated by hypermail 2b29 : Fri May 23 2003 - 22:00:34 EST