linux-kernel - Re: [GIT PULL] KVM updates for the 2.6.38 merge window

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: <4D2C21FE.3000406@redhat.com>
Date:	Tue, 11 Jan 2011 11:25:18 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Marcelo Tosatti <mtosatti@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] KVM updates for the 2.6.38 merge window

On 01/10/2011 09:31 PM, Linus Torvalds wrote:
> On Mon, Jan 10, 2011 at 1:21 AM, Avi Kivity<avi@...hat.com>  wrote:
> >
> >  - asynchronous page faults, which allow a guest to continue processing
> >  interrupts even when its memory is being paged in; in the case of a Linux
> >  2.6.38+ guest, it will receive a notification that the host is servicing a
> >  page fault, and may switch into another guest process
>
> So quite frankly, I don't like how this was done.
>
> When you touch files like mm/memory.c, you don't just touch them. You
> get sign-offs and acks from the VM maintainers. Seriously.
>
> In this case, I pulled, looked, and then unpulled. I just don't want
> it, and I think the new FAULT_FLAG_MINOR is seriously mis-named and
> hacky.
>
> Is it about atomicity? Is it about IO?

IO.  It means, only allow a minor fault; fail for a major fault.  Can 
you suggest a better name?

>   Why wasn't I notified
> before-hand? Was Andrew cc'd?

Andrew and linux-mm were copied.  Rik was the only one who reviewed (and 
ack'ed) it.  I guess I should have explicitly asked for Nick's review.

How do you want to proceed?  I can pull this patch out and stub out the 
callers in kvm (which will neuter async page faults for the time being, 
but we can live with that), then fix it in the background, or we can try 
to resolve it now.

What are your issues with the patch?

-- 
error compiling committee.c: too many arguments to function

--
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/