Re: MOD_INC_USE_COUNT

Neilski (neil.conway@ukaea.org.uk)
Tue, 11 Nov 1997 11:48:08 +0000


.Maybe we could get a gcc hack using the __attribute__(())
.mechanism... say __attribute__((no_block)); any routine marked
.nonblocking would print a warning if it called a blocking routine. I
.understand this is a mechanism already build into gcc to support
.various system-dependent hacks...

This would be great if it would work. I think it's important to get the system
to handle the problem, rather than the programmers, who inevitably get lazy
or make mistakes when it comes to checking which routines block (and of course
non-blocking routines can become blocking routines in the fullness of time).

Going off on a (slight) tangent: what do people think about the idea of a bug
management system ? It's been something I've been thinking about for a while
(and perhaps is already in place?). Basically what I have in mind is a system
whereby someone keeps a list of *all* kernel bugs as they are discovered and
fixed, with a view to monitoring how and why the bugs got created in the first
place. This then (after some time) provides an opportunity for feedback to
reduce the birth-rate of the bugs...

This is of course already happening informally but might work better if
implemented formally? It's the same kind of thing that helped Intel to produce
new generations of chips without the *type* of bugs that caused problems in
earlier chips (yeah right ;-)))...

Just a thought...
Neil