Dave Wysochanski db023c4448 Add an open_mode to the vg struct for liblvm - enforce read / write semantics. ...

For now, a simple way to enforce the read/write semantics is to just save the
open mode of the VG.  If the caller uses lvm_vg_create, the mode is write.
The caller using lvm_vg_open can use either read or write to open the VG.
Once we have this, we enforce the permissions on each API call and don't allow
a caller to modify a VG that has not been opened properly.

This may be better combined with the locking mode, but I view that as future
cleanup, past this initial release.  The intial release should enforce the
basic object semantics though, as described in the lvm.h file.

Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>

2009-07-28 15:14:56 +00:00

..

.exported_symbols

Add lvm_vg_get_seqno, updating lvm.h and unit test.

2009-07-28 13:17:04 +00:00

liblvm2app.pc.in

check in the correct pkgconfig file

2009-07-23 01:41:53 +00:00

lvm_base.c

Update lvm.h - remove remaining FIXMEs, note limitations of a few functions.

2009-07-28 13:16:40 +00:00

lvm_lv.c

Add an open_mode to the vg struct for liblvm - enforce read / write semantics.

2009-07-28 15:14:56 +00:00

lvm_pv.c

Use dm_malloc and dm_free in liblvm instead of malloc/free.

2009-07-28 09:56:48 +00:00

lvm_vg.c

Add an open_mode to the vg struct for liblvm - enforce read / write semantics.

2009-07-28 15:14:56 +00:00

lvm.h

Add lvm_vg_get_seqno, updating lvm.h and unit test.

2009-07-28 13:17:04 +00:00

Makefile.in

Add lvm_{pv|vg|lv}_get_{uuid|name}.

2009-07-23 23:40:05 +00:00