)]}'
{
  "commit": "7032027f1f5b8505b17b62e2607d81146ac7d8f8",
  "tree": "deb276d5fc25ae68fdee973edf88ec47bd32a327",
  "parents": [
    "821dc37f3f24c6cc1d3b8c9b9e70db810f532bcc"
  ],
  "author": {
    "name": "Stephen Smalley",
    "email": "sds@tycho.nsa.gov",
    "time": "Tue Dec 19 15:23:55 2017 -0500"
  },
  "committer": {
    "name": "Andrew Boie",
    "email": "andrewboie@gmail.com",
    "time": "Wed Feb 14 13:06:21 2018 -0800"
  },
  "message": "tests: userspace: fix read/write privileged stack tests\n\nThe read/write_kernel_stack tests are confusingly named and incorrectly\nimplemented for ARM; they are intended to test that user mode threads\ncannot read or write their privileged stacks.  The privileged stacks\non ARM are not relative to the user stack, and thus their location\ncannot be computed from the user stack.  To find the privileged stack on\nARM, we have to use _k_priv_stack_find(), which we do during setup\nin test_main() rather than from the usermode thread itself.  Accessing\nthread_stack directly from the test function requires making it\nnon-static in ztest, so we also give it a ztest_ prefix to avoid\ncollisions with other test programs.  Rename the test functions and\nglobal pointer variable to more accurately reflect their purpose.\n\nSigned-off-by: Stephen Smalley \u003csds@tycho.nsa.gov\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dbef1f2b400be6562529df8ed1b520d6d1b42f6a",
      "old_mode": 33188,
      "old_path": "tests/kernel/mem_protect/userspace/src/main.c",
      "new_id": "ca4447d95ff1d37b1cc981d2b0a7fabbecf0cb6c",
      "new_mode": 33188,
      "new_path": "tests/kernel/mem_protect/userspace/src/main.c"
    },
    {
      "type": "modify",
      "old_id": "9a1f16528bb82b8e44c021f12954e2a472ef1e86",
      "old_mode": 33188,
      "old_path": "tests/ztest/src/ztest.c",
      "new_id": "2284493cd27f2201280a9b754ae3bba76519e197",
      "new_mode": 33188,
      "new_path": "tests/ztest/src/ztest.c"
    }
  ]
}