> > > > Woah! Hm, this is going to cause lots of problems in drivers that have
> > > > been assuming that the BKL is grabbed during module unload, and during
> > > > open(). Hm, time to just fallback on the argument, "module
> > > > unloading is unsafe" :(
> > >
> > > Note that its the same in 2.4 as well. iirc, the BKL was removed from
> > > module loading/unloading sometime in the 2.3 timeline.
> >
> > Surely no recent code should be making that assumption anyway - the
> > BKL is being removed all over the place.
>
> The TTY layer isn't "recent code", its "very old code"
Oh, I know, I was just thinking aloud and not making much sense, ( :-)
) - what I really meant was is anybody writing new code without the
near-future BKL changes in mind, and if so, shouldn't it be avoided
now to save work in 2.7? I.E. is the BKL officially depreciated?
> and (IMO) removing the BKL from the TTY layer is a far from trivial
> matter.
>
> I believe at this point in the 2.5 cycle, we should not be looking
> to remove the BKL.
I think there were hints in another thread of a TTY layer overhaul in
2.7.
John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:54 EST