From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
linuxppc-dev@ozlabs.org, kvm@vger.kernel.org,
alex.williamson@redhat.com, agraf@suse.de, aik@ozlabs.ru
Subject: Re: [PATCH 2/2] drivers/vfio: Support EEH error injection
Date: Thu, 12 Mar 2015 16:01:05 +1100 [thread overview]
Message-ID: <20150312050105.GB28256@shangw> (raw)
In-Reply-To: <20150312042129.GS11973@voom.redhat.com>
On Thu, Mar 12, 2015 at 03:21:29PM +1100, David Gibson wrote:
>On Thu, Mar 12, 2015 at 02:16:42PM +1100, Gavin Shan wrote:
>> On Thu, Mar 12, 2015 at 11:57:21AM +1100, David Gibson wrote:
>> >On Wed, Mar 11, 2015 at 05:34:11PM +1100, Gavin Shan wrote:
>> >> The patch adds one more EEH sub-command (VFIO_EEH_PE_INJECT_ERR)
>> >> to inject the specified EEH error, which is represented by
>> >> (struct vfio_eeh_pe_err), to the indicated PE for testing purpose.
>> >>
>> >> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>> >> ---
>> >> Documentation/vfio.txt | 47 ++++++++++++++++++++++++++++++-------------
>> >> drivers/vfio/vfio_spapr_eeh.c | 14 +++++++++++++
>> >> include/uapi/linux/vfio.h | 34 ++++++++++++++++++++++++++++++-
>> >> 3 files changed, 80 insertions(+), 15 deletions(-)
>> >>
>> >> diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
>> >> index 96978ec..2e7f736 100644
>> >> --- a/Documentation/vfio.txt
>> >> +++ b/Documentation/vfio.txt
>> >> @@ -328,7 +328,13 @@ So 4 additional ioctls have been added:
>> >>
>> >> The code flow from the example above should be slightly changed:
>> >>
>> >> - struct vfio_eeh_pe_op pe_op = { .argsz = sizeof(pe_op), .flags = 0 };
>> >> + struct vfio_eeh_pe_op *pe_op;
>> >> + struct vfio_eeh_pe_err *pe_err;
>> >> +
>> >> + pe_op = malloc(sizeof(*pe_op) + sizeof(*pe_err));
>> >> + pe_err = (void *)pe_op + sizeof(*pe_op);
>> >> + pe_op->argsz = sizeof(*pe_op) + sizeof(*pe_err);
>> >
>> >Surely that argsz can't be correct for most of the operations. The
>> >extended structure should only be there for the error inject ioctl,
>> >yes?
>> >
>>
>> argsz isn't appropriate for most cases because kernel has the check
>> "expected_argsz < passed_argsz", not "expected_argsz ==
>> passed_argsz".
>
>It works for now, but if any of those calls was extended with more
>data, it would break horribly. By setting the argsz greater than
>necessary, you're effectively passing uninitialized data to the
>ioctl(). At the moment, the ioctl() ignores it, but the whole point
>of the argsz value is that in the future, it might not.
>
Thank you for more explanation. I agree that it's worthy to pass precise
argument size. I'll fix it as below in next revision:
>> However, I'll fix it as follows to avoid confusion after collecting
>> more comments:
>>
>> struct vfio_eeh_pe_op *pe_op;
>> struct vfio_eeh_pe_err *pe_err;
>>
>> /* For all cases except error injection */
>> pe_op = malloc(sizeof(*pe_op));
>> pe_op->argsz = sizeof(*pe_op);
>>
>> /* For error injection case here */
>> pe_op = realloc(sizeof(*pe_op) + sizeof(*pe_err));
>> pe_op->argsz = sizeof(*pe_op) + sizeof(*pe_err);
>> pe_err = (void *)pe_op + sizeof(*pe_op);
>>
Thanks,
Gavin
>
>--
>David Gibson | I'll have my music baroque, and my code
>david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> | _way_ _around_!
>http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2015-03-12 5:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 6:34 [PATCH 1/2] powerpc/eeh: Introduce eeh_pe_inject_err() Gavin Shan
2015-03-11 6:34 ` [PATCH 2/2] drivers/vfio: Support EEH error injection Gavin Shan
2015-03-12 0:57 ` David Gibson
2015-03-12 3:16 ` Gavin Shan
2015-03-12 4:21 ` David Gibson
2015-03-12 5:01 ` Gavin Shan [this message]
2015-03-13 20:28 ` Alex Williamson
2015-03-15 22:49 ` Gavin Shan
2015-03-16 1:01 ` David Gibson
2015-03-13 20:35 ` Alex Williamson
2015-03-15 22:55 ` Gavin Shan
2015-03-13 20:28 ` [PATCH 1/2] powerpc/eeh: Introduce eeh_pe_inject_err() Alex Williamson
2015-03-15 22:39 ` Gavin Shan
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=20150312050105.GB28256@shangw \
--to=gwshan@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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