linux-kernel - Re: [PATCH] always assign userspace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49247E43.1070108@codemonkey.ws>
Date:	Wed, 19 Nov 2008 14:59:47 -0600
From:	Anthony Liguori <anthony@...emonkey.ws>
To:	Glauber Costa <glommer@...hat.com>
CC:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org, avi@...hat.com
Subject: Re: [PATCH] always assign userspace_addr

Glauber Costa wrote:
> On Wed, Nov 19, 2008 at 12:51:00PM -0600, Anthony Liguori wrote:
>   
>> But the problem still exists even with this code.  I checked.
>>
>> So if you have something working without modifying the kernel, can you  
>> post it?
>>
>> Regards,
>>
>> Anthony Liguori
>>     
>
> Ok, how do you feel about this one?
>
> My proposal is to always delete a memslot before reusing the space,
> but controlling this behaviour by a flag, so we can maintain backwards
> compatibility with people using older versions of the interface.
>   

Is the old behavior ever correct?  I think it's always wrong.

Regards,

Anthony Liguori


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/