driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: "Zhao, Yakui" <yakui.zhao@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, Gao@osuosl.org,
	Shiqing <shiqing.gao@intel.com>,
	Jason Chen CJ <jason.cj.chen@intel.com>
Subject: Re: [RFC PATCH 09/15] drivers/acrn: add passthrough device support
Date: Mon, 2 Sep 2019 08:18:35 +0800	[thread overview]
Message-ID: <32aef63c-725a-09ff-5419-179eb8bd534a@intel.com> (raw)
In-Reply-To: <20190816130546.GA3632@kadam>



On 2019年08月16日 21:05, Dan Carpenter wrote:
> On Fri, Aug 16, 2019 at 10:25:50AM +0800, Zhao Yakui wrote:
>> +	case IC_ASSIGN_PTDEV: {
>> +		unsigned short bdf;
>> +
>> +		if (copy_from_user(&bdf, (void *)ioctl_param,
> 
> This casting is ugly and you also need a __user tag for Sparse.  Do
> something like "void __user *p = ioctl_param;"

Sure. The __user tag will be added for the ioctl_param parameter of 
copy_from/to_user.

> 
>> +				   sizeof(unsigned short)))
>> +			return -EFAULT;
>> +
>> +		ret = hcall_assign_ptdev(vm->vmid, bdf);
>> +		if (ret < 0) {
>> +			pr_err("acrn: failed to assign ptdev!\n");
>> +			return -EFAULT;
> 
> Preserve the error code.  "return ret;".
Ok. It will preserver the err code.

> 
>> +		}
>> +		break;
>> +	}
>> +	case IC_DEASSIGN_PTDEV: {
>> +		unsigned short bdf;
>> +
>> +		if (copy_from_user(&bdf, (void *)ioctl_param,
>> +				   sizeof(unsigned short)))
>> +			return -EFAULT;
>> +
>> +		ret = hcall_deassign_ptdev(vm->vmid, bdf);
>> +		if (ret < 0) {
>> +			pr_err("acrn: failed to deassign ptdev!\n");
>> +			return -EFAULT;
>> +		}
>> +		break;
>> +	}
>> +
>> +	case IC_SET_PTDEV_INTR_INFO: {
>> +		struct ic_ptdev_irq ic_pt_irq;
>> +		struct hc_ptdev_irq *hc_pt_irq;
>> +
>> +		if (copy_from_user(&ic_pt_irq, (void *)ioctl_param,
>> +				   sizeof(ic_pt_irq)))
>> +			return -EFAULT;
>> +
>> +		hc_pt_irq = kmalloc(sizeof(*hc_pt_irq), GFP_KERNEL);
>> +		if (!hc_pt_irq)
>> +			return -ENOMEM;
>> +
>> +		memcpy(hc_pt_irq, &ic_pt_irq, sizeof(*hc_pt_irq));
> 
> Use memdup_user().

OK. The memdup_user will be used.

> 
>> +
>> +		ret = hcall_set_ptdev_intr_info(vm->vmid,
>> +						virt_to_phys(hc_pt_irq));
>> +		kfree(hc_pt_irq);
>> +		if (ret < 0) {
>> +			pr_err("acrn: failed to set intr info for ptdev!\n");
>> +			return -EFAULT;
>> +		}
>> +
>> +		break;
>> +	}
> 
> regards,
> dan carpenter
> 
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2019-09-02  0:26 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16  2:25 [RFC PATCH 00/15] acrn: add the ACRN driver module Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 01/15] x86/acrn: Report X2APIC for ACRN guest Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 02/15] x86/acrn: Add two APIs to add/remove driver-specific upcall ISR handler Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 03/15] x86/acrn: Add hypercall for ACRN guest Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 04/15] drivers/acrn: add the basic framework of acrn char device driver Zhao Yakui
2019-08-16  7:05   ` Greg KH
2019-08-19  4:02     ` Zhao, Yakui
2019-08-19  5:26       ` Greg KH
2019-08-16 11:28   ` Dan Carpenter
2019-08-16  2:25 ` [RFC PATCH 05/15] drivers/acrn: add driver-specific hypercall for ACRN_HSM Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 06/15] drivers/acrn: add the support of querying ACRN api version Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 07/15] drivers/acrn: add acrn vm/vcpu management for ACRN_HSM char device Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 08/15] drivers/acrn: add VM memory management for ACRN " Zhao Yakui
2019-08-16 12:58   ` Dan Carpenter
2019-08-19  5:32     ` Zhao, Yakui
2019-08-19  7:39       ` Dan Carpenter
2019-08-19  7:46         ` Borislav Petkov
2019-08-20  2:25         ` Zhao, Yakui
2019-08-16  2:25 ` [RFC PATCH 09/15] drivers/acrn: add passthrough device support Zhao Yakui
2019-08-16 13:05   ` Dan Carpenter
2019-09-02  0:18     ` Zhao, Yakui [this message]
2019-08-16  2:25 ` [RFC PATCH 10/15] drivers/acrn: add interrupt injection support Zhao Yakui
2019-08-16 13:12   ` Dan Carpenter
2019-08-19  4:59     ` Zhao, Yakui
2019-08-16  2:25 ` [RFC PATCH 11/15] drivers/acrn: add the support of handling emulated ioreq Zhao Yakui
2019-08-16 13:39   ` Dan Carpenter
2019-08-19  4:54     ` Zhao, Yakui
2019-08-16  2:25 ` [RFC PATCH 12/15] drivers/acrn: add driver-specific IRQ handle to dispatch IO_REQ request Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 13/15] drivers/acrn: add service to obtain Power data transition Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 14/15] drivers/acrn: add the support of irqfd and eventfd Zhao Yakui
2019-08-16  2:25 ` [RFC PATCH 15/15] drivers/acrn: add the support of offline SOS cpu Zhao Yakui
2019-08-19 10:34   ` Dan Carpenter
2019-08-20  2:23     ` Zhao, Yakui
2019-08-16  6:39 ` [RFC PATCH 00/15] acrn: add the ACRN driver module Borislav Petkov
2019-08-16  7:03   ` Greg KH
2019-08-19  2:39     ` Zhao, Yakui
2019-08-19  5:25       ` Greg KH
2019-08-19  1:44   ` Zhao, Yakui
2019-08-19  5:25     ` Greg KH
2019-08-19  5:39       ` Zhao, Yakui
2019-08-19  6:18     ` Borislav Petkov

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=32aef63c-725a-09ff-5419-179eb8bd534a@intel.com \
    --to=yakui.zhao@intel.com \
    --cc=Gao@osuosl.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jason.cj.chen@intel.com \
    --cc=shiqing.gao@intel.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).