>>> On 21.01.19 at 13:03, <jbeul...@suse.com> wrote:
>>>> On 20.01.19 at 22:18, <christopher.w.cl...@gmail.com> wrote:
>> The "no repeated checks" problem also occurs when another separate
>> struct contains a field of a type that has already been checked:
>> whichever CHECK is performed second will break.
>>
>> eg.
>> typedef struct xen_argo_ring_data_ent
>> {
>> struct xen_argo_addr ring;
>> uint16_t flags;
>> uint16_t pad;
>> uint32_t space_required;
>> uint32_t max_message_size;
>> } xen_argo_ring_data_ent_t;
>>
>> also has a field of type xen_argo_addr, which produces CHECK_argo_addr,
>> which then fails because that was already tested in
>> CHECK_argo_send_addr.
>
> Hmm, I think the mcinfo example above contradicts this, because
> struct mcinfo_common is used by multiple other structures.
Due to
CHECK_mcinfo_common;
# undef xen_mcinfo_common
# undef CHECK_mcinfo_common
# define CHECK_mcinfo_common struct mcinfo_common
which I think would be easy enough to use in your case as well
(until we could perhaps get around and address the underlying
issue, albeit it's not really clear to me how that should be done).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
