From: Alex Williamson <alex.williamson@redhat.com>
To: JianChunfu <chunfu.jian@shingroup.cn>
Cc: cohuck@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, shenghui.qu@shingroup.cn
Subject: Re: [PATCH] vfio/pci: Separate INTx-enabled vfio_pci_device from unenabled to make the code logic clearer.
Date: Mon, 20 Nov 2023 10:38:48 -0700 [thread overview]
Message-ID: <20231120103848.337b6833.alex.williamson@redhat.com> (raw)
In-Reply-To: <20231120031752.522139-1-chunfu.jian@shingroup.cn>
On Mon, 20 Nov 2023 11:17:52 +0800
JianChunfu <chunfu.jian@shingroup.cn> wrote:
> It seems a little unclear when dealing with vfio_intx_set_signal()
> because of vfio_pci_device which is irq_none,
> so separate the two situations.
>
> Signed-off-by: JianChunfu <chunfu.jian@shingroup.cn>
> ---
> drivers/vfio/pci/vfio_pci_intrs.c | 31 +++++++++++++++----------------
> 1 file changed, 15 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
> index 6069a11fb51a..b6d126c48393 100644
> --- a/drivers/vfio/pci/vfio_pci_intrs.c
> +++ b/drivers/vfio/pci/vfio_pci_intrs.c
> @@ -468,6 +468,8 @@ static int vfio_pci_set_intx_trigger(struct vfio_pci_core_device *vdev,
> unsigned index, unsigned start,
> unsigned count, uint32_t flags, void *data)
> {
> + int32_t fd = *(int32_t *)data;
This is a null pointer dereference if anyone were to use
VFIO_IRQ_SET_DATA_NONE. Note this is also invalid for
VFIO_IRQ_SET_DATA_BOOL. I think this is largely why the function has
the current layout.
> +
> if (is_intx(vdev) && !count && (flags & VFIO_IRQ_SET_DATA_NONE)) {
> vfio_intx_disable(vdev);
> return 0;
> @@ -476,28 +478,25 @@ static int vfio_pci_set_intx_trigger(struct vfio_pci_core_device *vdev,
> if (!(is_intx(vdev) || is_irq_none(vdev)) || start != 0 || count != 1)
> return -EINVAL;
>
> - if (flags & VFIO_IRQ_SET_DATA_EVENTFD) {
> - int32_t fd = *(int32_t *)data;
> + if (!is_intx(vdev)) {
> int ret;
> + if (flags & VFIO_IRQ_SET_DATA_EVENTFD) {
@ret should be scoped within this branch with this layout and there
should be a blank line after variable declaration.
> + ret = vfio_intx_enable(vdev);
> + if (ret)
> + return ret;
>
> - if (is_intx(vdev))
> - return vfio_intx_set_signal(vdev, fd);
> + ret = vfio_intx_set_signal(vdev, fd);
> + if (ret)
> + vfio_intx_disable(vdev);
>
> - ret = vfio_intx_enable(vdev);
> - if (ret)
> return ret;
> -
> - ret = vfio_intx_set_signal(vdev, fd);
> - if (ret)
> - vfio_intx_disable(vdev);
> -
> - return ret;
> + } else
> + return -EINVAL;
Single line branches also get braces if the previous branch required
braces. Thanks,
Alex
> }
>
> - if (!is_intx(vdev))
> - return -EINVAL;
> -
> - if (flags & VFIO_IRQ_SET_DATA_NONE) {
> + if (flags & VFIO_IRQ_SET_DATA_EVENTFD) {
> + return vfio_intx_set_signal(vdev, fd);
> + } else if (flags & VFIO_IRQ_SET_DATA_NONE) {
> vfio_send_intx_eventfd(vdev, NULL);
> } else if (flags & VFIO_IRQ_SET_DATA_BOOL) {
> uint8_t trigger = *(uint8_t *)data;
prev parent reply other threads:[~2023-11-20 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 3:17 [PATCH] vfio/pci: Separate INTx-enabled vfio_pci_device from unenabled to make the code logic clearer JianChunfu
2023-11-20 17:38 ` Alex Williamson [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=20231120103848.337b6833.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=chunfu.jian@shingroup.cn \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shenghui.qu@shingroup.cn \
/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).