)]}'
{
  "log": [
    {
      "commit": "7fe2b3190b8b299409f13cf3a6f85c2bd371f8bb",
      "tree": "36af13880f834cd1c7fd92200ebcc33c64d9edf0",
      "parents": [
        "b0483e78e5c4c9871fc5541875b3bc006846d46b"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Feb 24 11:08:18 2010 -0600"
      },
      "committer": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Feb 24 11:46:53 2010 -0600"
      },
      "message": "dlm: fix ordering of bast and cast\n\nWhen both blocking and completion callbacks are queued for lock,\nthe dlm would always deliver the completion callback (cast) first.\nIn some cases the blocking callback (bast) is queued before the\ncast, though, and should be delivered first.  This patch keeps\ntrack of the order in which they were queued and delivers them\nin that order.\n\nThis patch also keeps track of the granted mode in the last cast\nand eliminates the following bast if the bast mode is compatible\nwith the preceding cast mode.  This happens when a remotely mastered\nlock is demoted, e.g. EX-\u003eNL, in which case the local node queues\na cast immediately after sending the demote message.  In this way\na cast can be queued for a mode, e.g. NL, that makes an in-transit\nbast extraneous.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\n"
    },
    {
      "commit": "fd22a51bcc0b7b76fc729b02316214fd979f9fe1",
      "tree": "e23326bb9df7cf0ee76b3b6b61c82364ff0aed78",
      "parents": [
        "03339696314fffb95dafb349b84243358e945ce6"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Tue Dec 09 11:55:46 2008 -0600"
      },
      "committer": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Tue Dec 23 10:16:46 2008 -0600"
      },
      "message": "dlm: improve how bast mode handling\n\nThe lkb bastmode value is set in the context of processing the\nlock, and read by the dlm_astd thread.  Because it\u0027s accessed\nin these two separate contexts, the writing/reading ought to\nbe done under a lock.  This is simple to do by setting it and\nreading it when the lkb is added to and removed from dlm_astd\u0027s\ncallback list which is properly locked.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\n"
    },
    {
      "commit": "dc68c7ed362a00a48290252573a8eb9f74463c3a",
      "tree": "99b8b64ea08d4990373d09e01b7bac2566ad3879",
      "parents": [
        "0f8e0d9a317406612700426fad3efab0b7bbc467"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Mon Aug 18 11:43:30 2008 -0500"
      },
      "committer": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Thu Aug 28 11:49:43 2008 -0500"
      },
      "message": "dlm: detect available userspace daemon\n\nIf dlm_controld (the userspace daemon that controls the setup and\nrecovery of the dlm) fails, the kernel should shut down the lockspaces\nin the kernel rather than leaving them running.  This is detected by\nhaving dlm_controld hold a misc device open while running, and if\nthe kernel detects a close while the daemon is still needed, it stops\nthe lockspaces in the kernel.\n\nKnowing that the userspace daemon isn\u0027t running also allows the\nlockspace create/remove routines to avoid waiting on the daemon\nfor join/leave operations.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\n"
    },
    {
      "commit": "0f8e0d9a317406612700426fad3efab0b7bbc467",
      "tree": "b4ed35afeab36615e50d5c7928a6199780fd2fca",
      "parents": [
        "4c246edd2550304df5b766cc841584b2bb058843"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Aug 06 13:30:24 2008 -0500"
      },
      "committer": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Thu Aug 28 11:49:15 2008 -0500"
      },
      "message": "dlm: allow multiple lockspace creates\n\nAdd a count for lockspace create and release so that create can\nbe called multiple times to use the lockspace from different places.\nAlso add the new flag DLM_LSFL_NEWEXCL to create a lockspace with\nthe previous behavior of returning -EEXIST if the lockspace already\nexists.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\n"
    },
    {
      "commit": "597d0cae0f99f62501e229bed50e8149604015bb",
      "tree": "b6cab09ff6fe2246740848164c0a52d5c03136a0",
      "parents": [
        "2eb168ca94aba3bcae350ad9b31870955174a218"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Jul 12 16:44:04 2006 -0500"
      },
      "committer": {
        "name": "Steven Whitehouse",
        "email": "swhiteho@redhat.com",
        "time": "Thu Jul 13 09:25:34 2006 -0400"
      },
      "message": "[DLM] dlm: user locks\n\nThis changes the way the dlm handles user locks.  The core dlm is now\naware of user locks so they can be dealt with more efficiently.  There is\nno more dlm_device module which previously managed its own duplicate copy\nof every user lock.\n\nSigned-off-by: Patrick Caulfield \u003cpcaulfie@redhat.com\u003e\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\nSigned-off-by: Steven Whitehouse \u003cswhiteho@redhat.com\u003e\n\n"
    }
  ]
}