> >>> phase one: disable auto-unload.
> >
> >> Phase 1 has been done.
> >
> > for the whole kernel?
>
> No. Only for this specific module.
right - my suggestion was that since this problem affects a
large class of modules, until that is fixed, we should
disable auto unload globally.
.mrg.
On Sun, 26 Jan 2014, matthew green wrote:
phase one: disable auto-unload.
Phase 1 has been done.
for the whole kernel?
No. Only for this specific module.
-
| Paul Goyette | PGP Key fingerprint: | E-mail
> > phase one: disable auto-unload.
> Phase 1 has been done.
for the whole kernel?
Phase 1 has been done.
On Sat, 25 Jan 2014, matthew green wrote:
Implement in-module ref-counting, and do not allow auto-unload if there
are existing references.
Note that manual unloading is not prevented.
OK christos@
XXX Also note that there is still a small window where the ref-count c
> >> Implement in-module ref-counting, and do not allow auto-unload if there
> >> are existing references.
> >>
> >> Note that manual unloading is not prevented.
> >>
> >> OK christos@
> >>
> >> XXX Also note that there is still a small window where the ref-count can
> >> XXX be decremented, an
> > Do you have any suggestion without boring work to rename all
> > #include lines and expand the "machine" path
> > in MI files to ${MACHINE}/include?
>
> I wish that cc/clang supported -isystem:NAME PATH and iquote:NAME PATH
> which would look starting at PATH for includes that start with {<,
