{"push_id":1313056249,"size":3,"distinct_size":2,"ref":"refs/heads/deadlock","head":"7488c082006fee9ce053d05edb4de7e391bed92b","before":"a1458de00e2ca2362a8211d727a123ac9d8c5d36","commits":[{"sha":"7090cf287847a808d6d0225bc9110f44c3248e12","author":{"name":"Joseph Fernandes","email":"0ab122cf48a67a6da98480a0689196deab54fca4@redhat.com"},"message":"tier/ctr/sql : Dafault values for sql cache and wal size\n\nSetting default values for sql cache and wal size\ncache : 12500 pages\nwal   : 25000 pages\n1 pages - 4096 bytes\n\nChange-Id: Iae3927e021af2e3f7617d45f84e81de3b7d93f1c\nBUG: 1377864\nSigned-off-by: Dan Lambright <dlambrig@redhat.com>\nReviewed-on: http://review.gluster.org/15536\nSmoke: Gluster Build System <jenkins@build.gluster.org>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.org>\nReviewed-by: Milind Changire <mchangir@redhat.com>","distinct":false,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/7090cf287847a808d6d0225bc9110f44c3248e12"},{"sha":"3b9f48e46071b2539628bafa87c315bb0905634f","author":{"name":"Anoop C S","email":"545712aeed095cc5358281eefdfc4ab80bcd58ee@redhat.com"},"message":"features/locks: Handle blocking lock requests properly\n\nChanges from commit 79db3aced2ffca84a696192343d5b811833eb671\nwere done in an attempt to avoid lock upgrade/downgrade\nproblems for a conflicting F_SETLKW lock request as explained\nbelow.\n\nConsider the following sequence of events acting upon a file:\n1. App1 requests shared blocking byte range lock request\n   from offset 0 to 5 and is granted.\n2. App2 requests shared blokcing byte range lock request\n   from offset 0 to 5 and is granted.\n3. App1 requests exclusive blocking byte range lock request\n   from offset 0 to 5 and is blocked.\n\nBefore the specified commit hash eventhough App2 releases its\nlock, App1's blocked lock request could not be granted due to\nlack of lock owner and related checks inside first_overlap()\nwhich is invoked from grant_blocked_locks() as soon as the\nrelease happens from App2. This undefined wait/hang was fixed\nvia the commit in such a way that we unlock App1's previously\nheld lock as soon as we receive a blocking lock request from\nApp1 which conflicts with App2's lock. This would mean that\nwe break the promise of granted shared lock given to App1\ntemporarily. pl_send_prelock_unlock() implements this early\nunlock.\n\nInstead we could have checked for lock owners and lock types\ninside first_overlap() to allow lock upgrades/downgrades from\nsame owner. The current patch partially reverts the specified\ncommit changes and adds this check inside first_overlap().\n\nChange-Id: I3ff349736bc5cb9b1dc53655b8fdbdd89aab3517\nBUG: 1291762\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/3b9f48e46071b2539628bafa87c315bb0905634f"},{"sha":"7488c082006fee9ce053d05edb4de7e391bed92b","author":{"name":"Anoop C S","email":"545712aeed095cc5358281eefdfc4ab80bcd58ee@redhat.com"},"message":"features/locks: Implement deadlock detection for POSIX locks\n\nTODO:\n* Clean up locks from blocked_lks as and when they are moved\n  out of ext_list.\n* Optimize newly added functions\n* Improve inline comments throughout the changes.\n\nChange-Id: I5e063149b5ee7e96bc36d543fce141295693fb86\nSigned-off-by: Anoop C S <anoopcs@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/7488c082006fee9ce053d05edb4de7e391bed92b"}]}
{"actor":{"display_login":"anoopcs9"}}