From: Dan Carpenter <dan.carpenter@oracle.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>
Subject: Re: [PATCH] vfio: Fix handling of error returned by 'vfio_group_get_from_dev()'
Date: Wed, 30 Nov 2016 21:27:07 +0300 [thread overview]
Message-ID: <20161130182707.GV6266@mwanda> (raw)
In-Reply-To: <20161130093646.0c68f7be@t450s.home>
On Wed, Nov 30, 2016 at 09:36:46AM -0700, Alex Williamson wrote:
> On Wed, 30 Nov 2016 08:06:12 +0100
> Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
>
> > 'vfio_group_get_from_dev()' seems to return only NULL on error, not an error
> > pointer.
> >
> > Fixes: 2169037dc322 ("vfio iommu: Added pin and unpin callback functions to vfio_iommu_driver_ops")
> > Fixes: c086de818dd8 ("vfio iommu: Add blocking notifier to notify DMA_UNMAP")
> >
> > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > ---
>
> Dan Carpenter proposed a nearly identical patch:
>
> http://www.spinics.net/lists/kvm/msg141468.html
>
> The difference is you return -ENODEV while Dan returns -EINVAL. I tend
> to prefer -ENODEV to distinguish this error case versus validation of
> the other parameters. This patch also identifies both commits
> introducing these, so I'm inclined to take this one rather than Dan's
> version. Dan & Kirti, I welcome any credits you'd like to apply to
> this patch for identifying and reviewing the same issue. Thanks,
>
Could I get a Reported-by?
thanks,
dan carpenter
next prev parent reply other threads:[~2016-11-30 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 7:06 [PATCH] vfio: Fix handling of error returned by 'vfio_group_get_from_dev()' Christophe JAILLET
2016-11-30 16:36 ` Alex Williamson
2016-11-30 18:27 ` Dan Carpenter [this message]
2016-11-30 18:39 ` Alex Williamson
2016-12-01 4:48 ` Kirti Wankhede
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=20161130182707.GV6266@mwanda \
--to=dan.carpenter@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
/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