[lvm-devel] [PATCH] (6/11) re-introduce vg_read

[Dave Wysochanski]

On Thu, 2008-10-30 at 19:08 +0100, Petr Rockai wrote:
> Hi,
> 
> this patch gets us back a function called vg_read, but this time it
> also does
> locking -- by default it grabs a read lock, as vg_read_for_update
> should be
> used when write lock is desired.
> 
> Yours,
>    Petr.
> 

It is a little confusing have a vg_read_for_update() (only intended for
WRITE) and a generic vg_read() (that allows both READ/WRITE) in the same
API.  Should we have "vg_read_for_update()" (WRITE) and
vg_read_for_query()" (READ) or something like that?