public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	<linux-kernel@vger.kernel.org>, Neo Jia <cjia@nvidia.com>,
	<kvm@vger.kernel.org>
Subject: Re: [PATCH] vfio-mdev: fix non-standard ioctl return val causing i386 build fail
Date: Wed, 4 Jan 2017 08:44:02 -0700	[thread overview]
Message-ID: <20170104084402.78fb7a75@t450s.home> (raw)
In-Reply-To: <33a0c8c2-3754-583d-230e-72d5d82650fb@nvidia.com>

On Wed, 4 Jan 2017 18:06:57 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:

> Thanks Paul for catching this.
> 
> In that case we should go with 'long' since mdev_parent_ops->ioctl() is
> called from vfio_device_ops->ioctl() for which the return type is 'long'.

Agreed, we're mirroring the struct file_operations definition of ioctl,
so the return should be a long.  Thanks,

Alex

> On 1/4/2017 1:06 AM, Paul Gortmaker wrote:
> > What appears to be a copy and paste error from the line above gets
> > the ioctl a ssize_t return value instead of the traditional "int".
> > 
> > The associated sample code used "long" which meant it would compile
> > for x86-64 but not i386, with the latter failing as follows:
> > 
> >   CC [M]  samples/vfio-mdev/mtty.o
> > samples/vfio-mdev/mtty.c:1418:20: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> >   .ioctl          = mtty_ioctl,
> >                     ^
> > samples/vfio-mdev/mtty.c:1418:20: note: (near initialization for ‘mdev_fops.ioctl’)
> > cc1: some warnings being treated as errors
> > 
> > Use the standard "int" ioctl return value in both the header and
> > the sample code to fix the issue.
> > 
> > Fixes: 9d1a546c53b4 ("docs: Sample driver to demonstrate how to use Mediated device framework.")
> > Cc: Kirti Wankhede <kwankhede@nvidia.com>
> > Cc: Neo Jia <cjia@nvidia.com>
> > Cc: Alex Williamson <alex.williamson@redhat.com>
> > Cc: kvm@vger.kernel.org
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> > ---
> >  include/linux/mdev.h     | 2 +-
> >  samples/vfio-mdev/mtty.c | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/linux/mdev.h b/include/linux/mdev.h
> > index 3ee44b8d2bb3..46659572ab00 100644
> > --- a/include/linux/mdev.h
> > +++ b/include/linux/mdev.h
> > @@ -78,7 +78,7 @@ struct mdev_parent_ops {
> >  			size_t count, loff_t *ppos);
> >  	ssize_t (*write)(struct mdev_device *mdev, const char __user *buf,
> >  			 size_t count, loff_t *ppos);
> > -	ssize_t (*ioctl)(struct mdev_device *mdev, unsigned int cmd,
> > +	int	(*ioctl)(struct mdev_device *mdev, unsigned int cmd,
> >  			 unsigned long arg);
> >  	int	(*mmap)(struct mdev_device *mdev, struct vm_area_struct *vma);
> >  };
> > diff --git a/samples/vfio-mdev/mtty.c b/samples/vfio-mdev/mtty.c
> > index 919c10d5b12e..6f0713b1f717 100644
> > --- a/samples/vfio-mdev/mtty.c
> > +++ b/samples/vfio-mdev/mtty.c
> > @@ -1147,7 +1147,7 @@ int mtty_get_device_info(struct mdev_device *mdev,
> >  	return 0;
> >  }
> >  
> > -static long mtty_ioctl(struct mdev_device *mdev, unsigned int cmd,
> > +static int mtty_ioctl(struct mdev_device *mdev, unsigned int cmd,
> >  			unsigned long arg)
> >  {
> >  	int ret = 0;
> >   

  reply	other threads:[~2017-01-04 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 19:36 [PATCH] vfio-mdev: fix non-standard ioctl return val causing i386 build fail Paul Gortmaker
2017-01-04 12:36 ` Kirti Wankhede
2017-01-04 15:44   ` Alex Williamson [this message]
2017-01-04 20:08     ` [PATCH v2] " Paul Gortmaker

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=20170104084402.78fb7a75@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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