lkml.org 
[lkml]   [2001]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Linux 2.4.1-ac15
Date
On Mon, 19 Feb 2001 11:35:08 +0000 (GMT), 
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>The problem isnt running module code. What happens in this case
>
> mod->next = module_list;
> module_list = mod; /* link it in */
>
>Note no write barrier.

<humour>It works on ix86 so the code must be right</humour>

>Delete is even worse
>
>We unlink the module
>We free the memory
>
>At the same time another cpu may be walking the exception table that we free.

Another good reason why locking modules via use counts from external
code is not the right fix. We definitely need a quiesce model for
module removal.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:15    [W:0.078 / U:11.440 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site