Re: [PATCH 6/9][cr][v2]: Checkpoint file-locks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Oren Laadan [orenl@xxxxxxxxxxxxxxx] wrote:
| 
| 
| > +	if (lock) {
| > +		h->fl_start = lock->fl_start;
| > +		h->fl_end = lock->fl_end;
| > +		h->fl_type = lock->fl_type;
| > +		h->fl_flags = lock->fl_flags;
| > +	} else {
| > +		/* Checkpoint a dummy lock as a marker */
| > +		h->fl_start = -1;
| 
| Maybe designate some constant for this ?  e.g. CKPT_FLOCK_NONE ?
| In any case, you need a (loff_t) -1  (like in the restore code).

Ok. Defining macros CKPT_HDR_SET_MARKER_LOCK() and
CKPT_HDR_CHECK_MARKER_LOCK().  Also added the missing (loff_t).
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux