Summary: mds: Fix invalid read [#3324]
Review request for Ticket(s): 3324
Peer Reviewer(s): Thang, Minh, Thien
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-3324
Base revision: 3beb5ab488600d4e4978084b8ea801a6de60ab15
Personal repository: git://git.code.sf.net/u/hieuhh/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 02037580ba403cb0afc66afb1e70c46c7210e21b
Author: hieu.h.hoang <hieu.h.ho...@dektech.com.au>
Date: Thu, 3 Nov 2022 10:07:09 +0700
mds: Test cases for conflicted vdests [#3324]
Verify the service events before and after conflict.
revision f5b653c6a77b0d43b647ef8930403645ff147bcd
Author: hieu.h.hoang <hieu.h.ho...@dektech.com.au>
Date: Thu, 3 Nov 2022 10:06:05 +0700
mds: Add a test function to wait for vdest events [#3324]
If vdest is installed with ownership enabled, a select object is provided
to notify incoming events. Before retrieving a event, polling the select
object to make sure the event arrived.
revision 81e23dd92464fbb8e880e48e38c033f5b02084d9
Author: hieu.h.hoang <hieu.h.ho...@dektech.com.au>
Date: Thu, 3 Nov 2022 07:23:26 +0700
mds: Fix invalid read [#3324]
After removing the active subscription result, mds finds
the next active subscription result by using the deleted
result. It led an invalid read. Solution is to get the
first active subscription result rather than the next
active result.
Complete diffstat:
------------------
src/mds/apitest/mdstipc.h | 1 +
src/mds/apitest/mdstipc_api.c | 481 +++++++++++++++++++++++++++++++++++++++++
src/mds/apitest/mdstipc_conf.c | 42 ++++
src/mds/mds_svc_op.c | 4 +-
4 files changed, 526 insertions(+), 2 deletions(-)
Testing Commands:
-----------------
*** LIST THE COMMAND LINE TOOLS/STEPS TO TEST YOUR CHANGES ***
Testing, Expected Results:
--------------------------
*** PASTE COMMAND OUTPUTS / TEST RESULTS ***
Conditions of Submission:
-------------------------
*** HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC ***
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
