linux-kernel - [PATCH][RESEND] KVM: fix undeclared MAY

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>] [day] [month] [year] [list]

Message-ID: <CAO_0yfOpkoznd=-wG=ay+knJ0_tVwziK_6QbTHX4-0TvsiXdCw@mail.gmail.com>
Date:	Sat, 24 Dec 2011 13:28:59 +0800
From:	Yang Bai <hamo.by@...il.com>
To:	avi@...hat.com, mtosatti@...hat.com
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	Yang Bai <hamo.by@...il.com>
Subject: [PATCH][RESEND] KVM: fix undeclared MAY_{READ,WRITE,ACCESS}

commit 08a95a511af91a2a6c42f2a8f13b99402a39e84b checksdevice
assignment permission but forgot to include thedefinition of
MAY_{READ,WRITE,ACCESS} in linux/fs.hInclude it and this fix the build
error here:http://buildbot.b1-systems.de/kvm/builders/i386/builds/401
Signed-off-by: Yang Bai <hamo.by@...il.com>--- virt/kvm/assigned-dev.c
|    1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/virt/kvm/assigned-dev.c b/virt/kvm/assigned-dev.cindex
da9690e..1d9dad0 100644--- a/virt/kvm/assigned-dev.c+++
b/virt/kvm/assigned-dev.c@@ -18,6 +18,7 @@ #include
<linux/interrupt.h> #include <linux/slab.h> #include
<linux/namei.h>+#include <linux/fs.h> #include "irq.h"  static struct
kvm_assigned_dev_kernel *kvm_find_assigned_dev(struct list_head
*head,-- 1.7.7.3

-- 
    """
    Keep It Simple,Stupid.
    """

Chinese Name: 白杨
Nick Name: Hamo
Homepage: http://hamobai.com/
GPG KEY ID: 0xA4691A33
Key fingerprint = 09D5 2D78 8E2B 0995 CF8E  4331 33C4 3D24 A469 1A33
--
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/