From: "Michael S. Tsirkin" <mst@redhat.com>
To: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"zhenzhong.duan@intel.com" <zhenzhong.duan@intel.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"peterx@redhat.com" <peterx@redhat.com>
Subject: Re: [PATCH v3 2/3] intel_iommu: fix type of the mask field in VTDIOTLBPageInvInfo
Date: Fri, 5 Jul 2024 06:16:26 -0400 [thread overview]
Message-ID: <20240705061549-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <61d45a7e-adb2-4d45-9879-549e4a258d75@eviden.com>
On Fri, Jul 05, 2024 at 09:52:48AM +0000, CLEMENT MATHIEU--DRIF wrote:
>
>
> On 05/07/2024 10:51, Michael S. Tsirkin wrote:
>
> Caution: External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
>
>
> On Fri, Jul 05, 2024 at 05:03:17AM +0000, CLEMENT MATHIEU--DRIF wrote:
>
> From: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
>
> VTDIOTLBPageInvInfo.mask might not fit in an uint8_t.
>
> I think what you mean is that is assigned values that might not
> fit .... it's u8 ATM so of course it fits.
>
> What about :
> "The mask stored into VTDIOTLBPageInvInfo.mask might not fit in an uint8_t. Use
> uint64_t to avoid overflows"
No, the mask stored there is u8.
You mean "that we are trying to store into ".
>
>
> Moreover, this field is used in binary operations with 64-bit addresses.
>
> So what?
>
> I thing the first part of the message is enough, the issue comes from the fact
> that the mask does not fit into the type
>
>
>
> Signed-off-by: Clément Mathieu--Drif <clement.mathieu--drif@eviden.com>
> ---
> hw/i386/intel_iommu_internal.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/i386/intel_iommu_internal.h b/hw/i386/intel_iommu_internal.h
> index cbc4030031..5fcbe2744f 100644
> --- a/hw/i386/intel_iommu_internal.h
> +++ b/hw/i386/intel_iommu_internal.h
> @@ -436,7 +436,7 @@ struct VTDIOTLBPageInvInfo {
> uint16_t domain_id;
> uint32_t pasid;
> uint64_t addr;
> - uint8_t mask;
> + uint64_t mask;
> };
> typedef struct VTDIOTLBPageInvInfo VTDIOTLBPageInvInfo;
>
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2024-07-05 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 5:03 [PATCH v3 0/3] VT-d minor fixes CLEMENT MATHIEU--DRIF
2024-07-05 5:03 ` [PATCH v3 1/3] intel_iommu: fix FRCD construction macro CLEMENT MATHIEU--DRIF
2024-07-05 8:47 ` Duan, Zhenzhong
2024-07-05 5:03 ` [PATCH v3 2/3] intel_iommu: fix type of the mask field in VTDIOTLBPageInvInfo CLEMENT MATHIEU--DRIF
2024-07-05 8:49 ` Duan, Zhenzhong
2024-07-05 8:51 ` Michael S. Tsirkin
2024-07-05 9:52 ` CLEMENT MATHIEU--DRIF
2024-07-05 10:16 ` Michael S. Tsirkin [this message]
2024-07-05 5:03 ` [PATCH v3 3/3] intel_iommu: make types match CLEMENT MATHIEU--DRIF
2024-07-05 8:51 ` Duan, Zhenzhong
2024-07-05 9:24 ` CLEMENT MATHIEU--DRIF
2024-07-05 9:42 ` Michael S. Tsirkin
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=20240705061549-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=jasowang@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.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;
as well as URLs for NNTP newsgroup(s).