On Sat, Aug 23, 2014 at 06:36:19AM -0400, Jeff Layton wrote: > The argument to locks_unlink_lock can't be just any pointer to a > pointer. It must be a pointer to the fl_next field in the previous > lock in the list. Looks good, Reviewed-by: Christoph Hellwig <hch@xxxxxx> This might explain some memory corruption I saw in the lease code while trying out a new creative (ab-)user of the lease code.. -- 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
