Menu

#343 userStatus parameter size in tlm_reply and tlm_replyQuery

2.1.0.0
closed
None
2021-08-11
2020-09-04
No

Hi ,
in tlm_reply and tlm_replyQuerythe argument userStatus is defined as an UINT16 insted an INT32 . This casting to UIN16 results in a bug, as negative values are changed.

Discussion

  • Bernd Löhr

    Bernd Löhr - 2020-09-08
    • status: open --> accepted
    • assigned_to: Bernd Löhr
     
  • Bernd Löhr

    Bernd Löhr - 2020-09-08

    The argument userStatus is defined as unsigned because the application's user reply status is defined to be ≥ 0 (see replyStatus in Table A.18 in IEC61375-2-3). Only the stack may send an ME with a negative reply value.
    This is no bug, but the parameter size should be changed to UINT32 with an error check (parameter/range error), if the supplied value is larger than 0x7FFFFFFF.

     
  • Bernd Löhr

    Bernd Löhr - 2020-09-08
    • summary: userStatus casting bug in tlm_reply e tlm_replyQuery --> userStatus parameter size in tlm_reply and tlm_replyQuery
     
  • Bernd Löhr

    Bernd Löhr - 2020-09-08

    Changed the ticket's title.

     
  • Bernd Löhr

    Bernd Löhr - 2020-09-11
    • status: accepted --> pending
     
  • Bernd Löhr

    Bernd Löhr - 2020-09-11

    Changed to UINT32 plus range check.

     
  • Stefan Bender

    Stefan Bender - 2021-07-29

    Tested by Inspection

     
  • Stefan Bender

    Stefan Bender - 2021-08-11
    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB