From: Ryan Cumming <ryan@spitfire.gotdns.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ioport-cache-2.6.8.1.patch
Date: Tue, 24 Aug 2004 12:38:26 -0700 [thread overview]
Message-ID: <200408241238.29702.ryan@spitfire.gotdns.org> (raw)
In-Reply-To: <20040824071928.GA7697@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
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.
-Ryan
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-24 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 21:23 [patch] lazy TSS's I/O bitmap copy Davide Libenzi
2004-08-23 21:32 ` Andi Kleen
2004-08-23 21:39 ` Davide Libenzi
2004-08-23 22:07 ` Linus Torvalds
2004-08-23 22:18 ` Davide Libenzi
2004-08-23 22:27 ` Linus Torvalds
2004-08-28 19:15 ` Alan Cox
2004-08-23 22:54 ` Davide Libenzi
2004-08-23 23:09 ` Linus Torvalds
2004-08-23 23:33 ` Davide Libenzi
2004-08-24 7:19 ` [patch] ioport-cache-2.6.8.1.patch Ingo Molnar
2004-08-24 15:15 ` Davide Libenzi
2004-08-24 19:38 ` Ryan Cumming [this message]
2004-08-24 20:20 ` Ingo Molnar
2004-08-24 1:53 ` [patch] lazy TSS's I/O bitmap copy Brian Gerst
2004-08-24 2:17 ` Linus Torvalds
2004-08-24 4:30 ` Davide Libenzi
2004-08-24 6:51 ` Arjan van de Ven
2004-08-24 15:13 ` Davide Libenzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408241238.29702.ryan@spitfire.gotdns.org \
--to=ryan@spitfire.gotdns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox