On Mon, Sep 3, 2018 at 8:12 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: > When encoding a file handle from lower nested overlayfs, prepending > another ovl_fh header for nested overlay file handle adds no new > information for decoding. Instead, we just set a 'nested' flag in ovl_fh > header for nested file handle, so we know to distinguish between real > upper file handle that should be decoded from real upper layer and > nested upper file handle that should be decoded from nested lower layer. > For the maximum allowed overlay nesting depth of 1, one bit is enough. This is an optimization, right? What are the user-visible advantages that would justify the added complexity? Thanks, Miklos
