This is the return code that setlease() currently returns when the lease can not be obtained. Although ENOTSUPP would be more accurately describing the error it will be a new return code from setlease() that is currently not expected by callers to setlease(), but either return code should work. Marc.
Steven Whitehouse <[EMAIL PROTECTED]> wrote on 06/09/2007 07:18:07 AM: > Hi, > > On Fri, 2007-06-08 at 18:14 -0400, J. Bruce Fields wrote: > > From: Marc Eshel <[EMAIL PROTECTED]> > > > > Since gfs2 can't prevent conflicting opens or leases on other nodes, we > > probably shouldn't allow it to give out leases at all. > > > > Put the newly defined lease operation into use in gfs2 by turning off > > lease, unless we're using the "nolock' locking module (in which case all > > locking is local anyway). > > > > Signed-off-by: Marc Eshel <[EMAIL PROTECTED]> > > In general it looks fine, but EAGAIN seems like an odd error to return > when we really mean that this function isn't supported in cluster mode. > Is that really the correct value for that? > > Steve. > > - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
