Messages in this thread | | | Date | Tue, 24 Aug 2004 22:20:42 +0200 | From | Ingo Molnar <> | Subject | Re: [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/
| |