>
> So section mismatch warnings are more about catching sloopy usage of __init than it is to
> catch potential kernel oopesen. But the latter is a nice side effect that is appreciated.
My point was that I cannot recall a single real oops bug found by the compile
time checking.
We had a few in the past, but since we poison init data after boot they all tended
to be found quickly anyways.
But the warnings just seem to require endless changes and bogus changes
(randomly moving code which was actually ok because it only called
in the init case).
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
