linux-kernel - Re: [PATCH v3 0/3] kvm: KVM_IRQFD cleanup, docs, sanitize flags

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]

Date:	Mon, 02 Jul 2012 09:51:51 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	avi@...hat.com
Cc:	mst@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	jan.kiszka@...mens.com, cornelia.huck@...ibm.com
Subject: Re: [PATCH v3 0/3] kvm: KVM_IRQFD cleanup, docs, sanitize flags

On Fri, 2012-06-29 at 09:56 -0600, Alex Williamson wrote:
> Before we start fiddling with what we can and can't add to KVM_IRQFD
> we need to figure out if anyone has been sloppy in their use of the
> ioctl flags.  This series has a minor cleanup to pass the struct
> kvm_irqfd to seup functions rather than individual parameters, making
> it more consistent with ioeventfd, adds API documentation for this
> ioctl, and sanitizes the flags.  If anyone screams, we may have to
> revert this last patch.  Thanks,

Avi, what do you think about trying to get this in for 3.5 to test
whether we break anyone?  Then we can aim for 3.6 for level irqfd &
eoifd support.  Thanks,

Alex

> ---
> 
> Alex Williamson (3):
>       kvm: Sanitize KVM_IRQFD flags
>       kvm: Add missing KVM_IRQFD API documentation
>       kvm: Pass kvm_irqfd to functions
> 
> 
>  Documentation/virtual/kvm/api.txt |   16 ++++++++++++++++
>  include/linux/kvm_host.h          |    4 ++--
>  virt/kvm/eventfd.c                |   23 +++++++++++++----------
>  virt/kvm/kvm_main.c               |    2 +-
>  4 files changed, 32 insertions(+), 13 deletions(-)



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