[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 3/3] libxl: use time_t for qmp_synchronous_send()'s last parameter

To: Jan Beulich <jbeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Juergen Gross <jgross@xxxxxxxx>
Date: Thu, 18 Aug 2022 16:20:01 +0200
Cc: Anthony Perard <anthony.perard@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>
Delivery-date: Thu, 18 Aug 2022 14:20:13 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 18.08.22 16:07, Jan Beulich wrote:

"int" is not a suitable type to hold / receive "time_t" values.

The parameter is presently unused, so no functional change.

Coverity ID: 1509377
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>


Reviewed-by: Juergen Gross <jgross@xxxxxxxx>

The severity of this issue is rather low IMO. A timeout of more than
60 years not being handled correctly seems to have no relevance at all.


Juergen

Attachment: OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Follow-Ups:
- Re: [PATCH 3/3] libxl: use time_t for qmp_synchronous_send()'s last parameter
  - From: Jan Beulich

References:
- [PATCH 0/3] tools: address recently reported Coverity issues
  - From: Jan Beulich
- [PATCH 3/3] libxl: use time_t for qmp_synchronous_send()'s last parameter
  - From: Jan Beulich

Prev by Date: Re: [PATCH] Use direct I/O for loop devices
Next by Date: Re: [PATCH] Use direct I/O for loop devices
Previous by thread: [PATCH 3/3] libxl: use time_t for qmp_synchronous_send()'s last parameter
Next by thread: Re: [PATCH 3/3] libxl: use time_t for qmp_synchronous_send()'s last parameter
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.