linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Xiang wangx <wangxiang@cdjrlc.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: Add const to file_operations
Date: Tue, 31 May 2022 19:47:06 +0000	[thread overview]
Message-ID: <YpZwum3FHCJKnWIQ@google.com> (raw)
In-Reply-To: <20220530020857.2565-1-wangxiang@cdjrlc.com>

On Mon, May 30, 2022, Xiang wangx wrote:
> Struct file_operations should normally be const.

Operative word being "should".  kvm_chardev_ops isn't constant because kvm_init()
modifies the "owner".  The same was true for kvm_vcpu_fops and kvm_vm_fops until
commit 70375c2d8fa3 ("Revert "KVM: set owner of cpu and vm file operations"").

So, this patch is both stale, and completely broken when applied against current
KVM as well as whatever old version of KVM it was generated with.

arch/x86/kvm/../../../virt/kvm/kvm_main.c:4873:37: error: conflicting type qualifiers for ‘kvm_chardev_ops’
 4873 | static const struct file_operations kvm_chardev_ops = {
      |                                     ^~~~~~~~~~~~~~~
arch/x86/kvm/../../../virt/kvm/kvm_main.c:120:31: note: previous declaration of ‘kvm_chardev_ops’ with type ‘struct file_operations’
  120 | static struct file_operations kvm_chardev_ops;
      |                               ^~~~~~~~~~~~~~~
arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function ‘kvm_init’:
arch/x86/kvm/../../../virt/kvm/kvm_main.c:5777:31: error: assignment of member ‘owner’ in read-only object
 5777 |         kvm_chardev_ops.owner = module;
      |                               ^
  CC      arch/x86/events/intel/p6.o
make[3]: *** [scripts/Makefile.build:288: arch/x86/kvm/../../../virt/kvm/kvm_main.o] Error 1
make[2]: *** [scripts/Makefile.build:550: arch/x86/kvm] Error 2


> Signed-off-by: Xiang wangx <wangxiang@cdjrlc.com>
> ---
>  virt/kvm/kvm_main.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 3f6d450355f0..7dc2433f1b01 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -3550,7 +3550,7 @@ static int kvm_vcpu_release(struct inode *inode, struct file *filp)
>  	return 0;
>  }
>  
> -static struct file_operations kvm_vcpu_fops = {
> +static const struct file_operations kvm_vcpu_fops = {
>  	.release        = kvm_vcpu_release,
>  	.unlocked_ioctl = kvm_vcpu_ioctl,
>  	.mmap           = kvm_vcpu_mmap,
> @@ -4599,7 +4599,7 @@ static long kvm_vm_compat_ioctl(struct file *filp,
>  }
>  #endif
>  
> -static struct file_operations kvm_vm_fops = {
> +static const struct file_operations kvm_vm_fops = {
>  	.release        = kvm_vm_release,
>  	.unlocked_ioctl = kvm_vm_ioctl,
>  	.llseek		= noop_llseek,
> @@ -4701,7 +4701,7 @@ static long kvm_dev_ioctl(struct file *filp,
>  	return r;
>  }
>  
> -static struct file_operations kvm_chardev_ops = {
> +static const struct file_operations kvm_chardev_ops = {
>  	.unlocked_ioctl = kvm_dev_ioctl,
>  	.llseek		= noop_llseek,
>  	KVM_COMPAT(kvm_dev_ioctl),
> -- 
> 2.36.1
> 

      reply	other threads:[~2022-05-31 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  2:08 [PATCH] KVM: Add const to file_operations Xiang wangx
2022-05-31 19:47 ` Sean Christopherson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YpZwum3FHCJKnWIQ@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=wangxiang@cdjrlc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).