Statistics
| Branch: | Tag: | Revision:

root @ af8492ff

Name Size
  autotools
  daemons
  devel
  doc
  lib
  man
  qa
  src
  test
  tools
.ghci 21 Bytes
.gitignore 2.6 kB
COPYING 17.6 kB
INSTALL 11.3 kB
Makefile.am 75 kB
NEWS 129.4 kB
README 191 Bytes
UPGRADE 12.4 kB
autogen.sh 283 Bytes
configure.ac 23.4 kB
epydoc.conf.in 444 Bytes
pylintrc 2.9 kB
pylintrc-test 2.9 kB

Latest revisions

# Date Author Comment
af8492ff 02/20/2014 11:11 am Michele Tartara

Add precise to build_chroot

Modify the build_chroot script to support Ubuntu Precise as a target
environment.

Signed-off-by: Michele Tartara <>
Reviewed-by: Helga Velroyen <>

956b83d6 02/20/2014 10:12 am Klaus Aehlig

Enforce the order restrictions on group locks

Disallow requests for an exclusive lock, if the owner already
holds a shared (and only shared) lock on a group lock that lock
belongs to.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Helga Velroyen <>

fe78783d 02/20/2014 10:12 am Klaus Aehlig

Document restrictions on lock implication

As owning a group lock has the same effect as owning a
group of locks, some restrictions have to be added to
to avoid dead locks. Document them.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Helga Velroyen <>

1ca6b451 02/19/2014 03:45 pm Klaus Aehlig

Efficiently verify consistent lock requests

Most requests for lock updates are consistent and mention
every lock only once. So verify this property efficiently
by comparing lengths. Only if the length do not coincide
go through the actual (quadratic) comparison to find a...

277c969f 02/19/2014 03:45 pm Klaus Aehlig

Add a test verifying that lock-implication is honored

Locks can be included in one another. This inclusion can be violated
in two ways, viz.,
- A holds a lock L and B holds an exclusive lock L belongs to, and
- A holds an exclusive lock and B holds a lock L belongs to....

381889dc 02/19/2014 03:45 pm Klaus Aehlig

Support lock implication in allocation

Make the module abstractly handling lock allocation
honor the additional restrictions caused by lock
implications.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Petr Pudlak <>

64df329d 02/19/2014 03:45 pm Klaus Aehlig

Verify that every owner mentioned as blocking actually is

If a request is blocked by multiple lock owners, verify that each
single one of them actually blocks the request. In other words,
verify that, whenever all but one release their lock, the request
still does not succeed....

9bf17b50 02/19/2014 03:45 pm Klaus Aehlig

Verify that the set of blocking owners is big enough

When a request is blocked, the list of blocking owners
should exhaust all blocking reasons, i.e., if those
owners release all their locks, the update must succeed.

Signed-off-by: Klaus Aehlig <>...

80004e70 02/19/2014 03:45 pm Klaus Aehlig

Add a convenience function to free all locks of an owner

While freeing all locks of a single owner can easily be defined
out of listLocks and updateLocks, it is worth having this function
in its own right. For example, it will be needed when the death of...

619b12df 02/19/2014 03:45 pm Klaus Aehlig

Make TestLock an instance of Lock

Equip the type of test locks with a simple group structure
consisting of two lock groups and a big lock.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Petr Pudlak <>

View all revisions | View revisions

Also available in: Atom