lkml.org 
[lkml]   [2007]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] Memory shortage can result in inconsistent flocks state
    On 9/13/07, Pavel Emelyanov <xemul@openvz.org> wrote:
    > J. Bruce Fields wrote:
    > > On Tue, Sep 11, 2007 at 04:38:13PM +0400, Pavel Emelyanov wrote:
    > >> This is a known feature that such "re-locking" is not atomic,
    > >> but in the racy case the file should stay locked (although by
    > >> some other process), but in this case the file will be unlocked.
    > >
    > > That's a little subtle (I assume you've never seen this actually
    > > happen?), but it makes sense to me.
    >
    > Well, this situation is hard to notice since usually programs
    > try to finish up when some error is returned from the kernel,
    > but I do believe that this could happen in one of the openvz
    > kernels since we limit the kernel memory usage for "containers"
    > and thus -ENOMEM is a common error.
    >

    The fault injection framework should be able to introduce the same
    error. Of course hitting the error would require careful setup of the
    fault parameters.

    Balbir
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-09-13 09:19    [W:0.020 / U:8.072 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site