Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

orcmd fails when adding a workflow with a long list of hostnames using octl #10

Open
barajas opened this issue Jul 20, 2017 · 0 comments
Labels

Comments

@barajas
Copy link
Contributor

barajas commented Jul 20, 2017

Description:

While adding a workflow containing a long list of host names separated by a comma, the workflow successfully sends the configuration to orcm daemon but the binary shows a memory corruption issue.

Note: The issue is not happening if the host names are configured using regex

Expected behavior:

orcm daemon memory should not be corrupted at any time.

Actual behavior:

orcm daemon sometimes shows a malloc memory corruption other times shows a double free corruption.

Reproduction steps:

$ orcmsched &
$ orcmd --omca sensor heartbeat,coretemp
$ octl workflow add w1.xml

Create the w1.xml using the configuration below:

<workflows>
    <aggregator>agg0000</aggregator>
    <workflow name="test">
        <step name="filter">
            <hostname>agg0000,node00000000,node00000001,node00000002,node00000003,node00000004,node00000005,node00000006,node00000007,node00000008,node00000009,node00000010,node00000011,node00000012,node00000013,node00000014,node00000015,node00000016,node00000017,node00000018,node00000019,node00000020,node00000021,node00000022,node00000023,node00000024,node00000025,node00000026,node00000027,node00000028,node00000029,node00000030,node00000031,node00000032,node00000033,node00000034,node00000035,node00000036,node00000037,node00000038,node00000039,node00000040,node00000041,node00000042,node00000043,node00000044,node00000045,node00000046,node00000047,node00000048,node00000049,node00000050,node00000051,node00000052,node00000053,node00000054,node00000055,node00000056,node00000057,node00000058,node00000059,node00000060,node00000061,node00000062,node00000063,node00000064,node00000065,node00000066,node00000067,node00000068,node00000069,node00000070,node00000071,node00000072,node00000073,node00000074,node00000075,node00000076,node00000077,node00000078,node00000079,node00000080,node00000081,node00000082,node00000083,node00000084,node00000085,node00000086,node00000087,node00000088,node00000089,node00000090,node00000091,node00000092,node00000093,node00000094,node00000095,node00000096,node00000097,node00000098,node00000099,node00000100,node00000101,node00000102,node00000103,node00000104,node00000105,node00000106,node00000107,node00000108,node00000109,node00000110,node00000111,node00000112,node00000113,node00000114,node00000115,node00000116,node00000117,node00000118,node00000119,node00000120,node00000121,node00000122,node00000123,node00000124,node00000125,node00000126,node00000127,node00000128,node00000129,node00000130,node00000131,node00000132,node00000133,node00000134,node00000135,node00000136,node00000137,node00000138,node00000139,node00000140,node00000141,node00000142,node00000143,node00000144,node00000145,node00000146,node00000147,node00000148,node00000149,node00000150,node00000151,node00000152,node00000153,node00000154,node00000155,node00000156,node00000157,node00000158,node00000159,node00000160,node00000161,node00000162,node00000163,node00000164,node00000165,node00000166,node00000167,node00000168,node00000169,node00000170,node00000171,node00000172,node00000173,node00000174,node00000175,node00000176,node00000177,node00000178,node00000179,node00000180,node00000181,node00000182,node00000183,node00000184,node00000185,node00000186,node00000187,node00000188,node00000189,node00000190,node00000191,node00000192,node00000193,node00000194,node00000195,node00000196,node00000197,node00000198,node00000199,node00000200,node00000201,node00000202,node00000203,node00000204,node00000205,node00000206,node00000207,node00000208,node00000209,node00000210,node00000211,node00000212,node00000213,node00000214,node00000215,node00000216,node00000217,node00000218,node00000219,node00000220,node00000221,node00000222,node00000223,node00000224,node00000225,node00000226,node00000227,node00000228,node00000229,node00000230,node00000231,node00000232,node00000233,node00000234,node00000235,node00000236,node00000237,node00000238,node00000239,node00000240,node00000241,node00000242,node00000243,node00000244,node00000245,node00000246,node00000247,node00000248,node00000249,node00000250,node00000251,node00000252,node00000253,node00000254,node00000255</hostname>
            <data_group>coretemp</data_group>
            <core>core[1:0-9],core[2:10-99],core[3:100-999]</core>
        </step>
        <step name="aggregate">
            <compute>min</compute>
            <db>yes</db>
        </step>
    </workflow>
</workflows>

You should see a malloc memory corruption or a double free corruption.

Specifications:

  • version: 58221bc
  • platform: CentOS 7.2
  • Component: orcmd
@ericho ericho added the bug label Jul 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants