Summary: clm: fix access uninitialised value [#3326]
Review request for Ticket(s): 3326
Peer Reviewer(s): Thang, Hieu
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-3326
Base revision: 2021d0c035d2989267ee8d0d8d826ddf53fc3201
Personal repository: git://git.code.sf.net/u/thienhuynh/review
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services y
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
*** EXPLAIN/COMMENT THE PATCH SERIES HERE ***
revision 04c6055e2e1c69257be8e4a7595d8a41de980a60
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Thu, 8 Dec 2022 08:35:53 +0700
log: fix access uninitialised value [#3326]
Struct SaVersionT has only 24bit but using encode 32bit.
Solution is encode each 8bit releaseCode, majorCode, minorCode
and one more 8bit to backward compatible.
revision 3973d5d808f4efd9f82c952e3b54e28fdb40d656
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed, 7 Dec 2022 16:43:41 +0700
imm: fix access uninitialised value [#3326]
revision 09a54396ff8bbef8de9118dbe88f4e7cafe65045
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed, 7 Dec 2022 16:42:03 +0700
ntf: fix access uninitialised value [#3326]
struct ntfsv_read_next_req_t has only 9 bytes but reserve space
take up 10 bytes.
solution is add a valid byte into uba space.
revision 3c0bd902ab74cfc9c3102cb5886b6ba7b29221ae
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed, 7 Dec 2022 16:41:41 +0700
mbc: fix access uninitialised value [#3326]
revision 71c34454d2e4e05ce1eb3a003d9474dd769a4529
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed, 7 Dec 2022 16:40:39 +0700
clm: fix access uninitialised value [#3326]
Complete diffstat:
------------------
src/clm/clmd/clms_evt.cc | 4 ++++
src/clm/clmd/clms_imm.cc | 3 +++
src/imm/immnd/immnd_evt.c | 3 +--
src/log/logd/lgs_mbcsv_v6.cc | 14 ++++++++++++--
src/mbc/mbcsv_act.c | 2 ++
src/mbc/mbcsv_api.c | 2 ++
src/mbc/mbcsv_tmr.c | 1 +
src/mbc/mbcsv_util.c | 7 +++++++
src/ntf/common/ntfsv_enc_dec.c | 1 +
9 files changed, 33 insertions(+), 4 deletions(-)
Testing Commands:
-----------------
N/A
Testing, Expected Results:
--------------------------
N/A
Conditions of Submission:
-------------------------
ACK from reviewer
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 y y
powerpc n n
powerpc64 n n
Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]
Your checkin has not passed review because (see checked entries):
___ Your RR template is generally incomplete; it has too many blank entries
that need proper data filled in.
___ You have failed to nominate the proper persons for review and push.
___ Your patches do not have proper short+long header
___ You have grammar/spelling in your header that is unacceptable.
___ You have exceeded a sensible line length in your headers/comments/text.
___ You have failed to put in a proper Trac Ticket # into your commits.
___ You have incorrectly put/left internal data in your comments/files
(i.e. internal bug tracking tool IDs, product names etc)
___ You have not given any evidence of testing beyond basic build tests.
Demonstrate some level of runtime or other sanity testing.
___ You have ^M present in some of your files. These have to be removed.
___ You have needlessly changed whitespace or added whitespace crimes
like trailing spaces, or spaces before tabs.
___ You have mixed real technical changes with whitespace and other
cosmetic code cleanup changes. These have to be separate commits.
___ You need to refactor your submission into logical chunks; there is
too much content into a single commit.
___ You have extraneous garbage in your review (merge commits etc)
___ You have giant attachments which should never have been sent;
Instead you should place your content in a public tree to be pulled.
___ You have too many commits attached to an e-mail; resend as threaded
commits, or place in a public tree for a pull.
___ You have resent this content multiple times without a clear indication
of what has changed between each re-send.
___ You have failed to adequately and individually address all of the
comments and change requests that were proposed in the initial review.
___ You have a misconfigured ~/.gitconfig file (i.e. user.name, user.email etc)
___ Your computer have a badly configured date and time; confusing the
the threaded patch review.
___ Your changes affect IPC mechanism, and you don't present any results
for in-service upgradability test.
___ Your changes affect user manual and documentation, your patch series
do not contain the patch that updates the Doxygen manual.
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
