Messages in this thread | | | Date | Mon, 7 Jun 2004 16:19:03 +0200 | From | Ingo Molnar <> | Subject | Re: WINE + NX (No eXecute) support for x86, 2.6.7-rc2-bk2 |
| |
* Christoph Hellwig <hch@infradead.org> wrote:
> > It seems Linus's kernel does that quite well, but some vendors seem not > > to care too much about breaking Wine. > > Why should they? You need to fix up the broken assumptions in wine.
for the record, i personally do care about Wine alot, and i'd like to repeat that exec-shield did not break any _existing_ binaries. It broke _newly_ compiled binaries that got the PT_GNU_STACK flag.
i can very well understand the frustration of the Wine people - dealing with such issues doesnt give a feeling of advance, because you are working on solving an issue that didnt exist before.
prelink might have broken other assumptions of Wine - one way around that is to compile Wine as a PIE binary (or to link it statically). prelink is a very important feature as well, from which Wine does benefit as well.
Wine is in a really difficult position (due to the complex task it achieves) and is more sensitive to VM layout changes than other applications. So lets try to find the solution that preserves the kernel's ability to further optimize the VM layout, while meeting Wine's desire to get a simple VM layout that is not mapped in the first 1 GB or so.
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/
| |