[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070316161853.GD9413@elte.hu>
Date: Fri, 16 Mar 2007 17:18:53 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Paulo Marques <pmarques@...popie.com>
Cc: Alexey Dobriyan <adobriyan@...ru>, akpm@...l.org,
linux-kernel@...r.kernel.org, devel@...nvz.org, tglx@...utronix.de,
viro@...iv.linux.org.uk, rusty@...tcorp.com.au
Subject: Re: [PATCH RESEND 2/2] Fix some kallsyms_lookup() vs rmmod races
* Paulo Marques <pmarques@...popie.com> wrote:
> >looking at the problem from another angle: wouldnt this be something
> >that would benefit from freeze_processes()/unfreeze_processes(), and
> >hence no locking would be required?
>
> I also considered this, but it seemed a little too "blunt" to stop
> everything (including completely unrelated processes and kernel
> threads) just to remove a module.
'just to remove a module' is very, very rare, on the timescale of most
kernel ops. Almost no distro does it. Furthermore, because we want to do
CPU-hotplug that way, we really want to make
freeze_processes()/unfreeze_processes() 'instantaneous' to the human -
and it is that already. (if it isnt in some case we can make it so)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists