lkml.org 
[lkml]   [2004]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] ioport-cache-2.6.8.1.patch

* Ryan Cumming <ryan@spitfire.gotdns.org> wrote:

> On Tuesday 24 August 2004 00:19, you wrote:
> > +       if (likely(next == tss->io_bitmap_owner)) {
>
> Probably a stupid question, but what's stopping the tss->io_bitmap_owner from being killed, and then a new
> thread_struct being kmalloc()'ed in the exact same place as the old one? I realize it's highly unlikely, I'm just
> wondering if it's possible at all.
>
> I guess clearing tss->io_bitmap_owner whenever we kfree() the bitmap owner's thread_struct would plug that up.

the patch flushes the ->io_bitmap_owner info on thread exit.

Ingo
-
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 14:05    [W:0.062 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site