RE: Buggy __free(kfree) usage pattern already in tree

[David Laight]

If this stuff is so hard to get right for non-trivial cases
perhaps it should all be ripped out?

The trivial cases are pretty easy to eve-ball check and
static analysis tools do a reasonable job.

Maybe I'm 'old-school' but I'd much rather see explicit
unlock() and free() than have 'some compiler magic' do
it for you.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)