summaryrefslogtreecommitdiffstats
path: root/samples/vfio-mdev
diff options
context:
space:
mode:
authorAmir Goldstein <amir73il@gmail.com>2017-10-24 12:24:11 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2017-10-24 16:06:17 +0200
commitfa0096e3bad69ed6f34843fd7ae1c45ca987012a (patch)
treebaef2db65b514249b1d5299bb8f9f3a2b872b48a /samples/vfio-mdev
parent7937a56fdf0b064c2ffa33025210f725a4ebc822 (diff)
downloadblackbird-op-linux-fa0096e3bad69ed6f34843fd7ae1c45ca987012a.tar.gz
blackbird-op-linux-fa0096e3bad69ed6f34843fd7ae1c45ca987012a.zip
ovl: do not cleanup unsupported index entries
With index=on, ovl_indexdir_cleanup() tries to cleanup invalid index entries (e.g. bad index name). This behavior could result in cleaning of entries created by newer kernels and is therefore undesirable. Instead, abort mount if such entries are encountered. We still cleanup 'stale' entries and 'orphan' entries, both those cases can be a result of offline changes to lower and upper dirs. When encoutering an index entry of type directory or whiteout, kernel was supposed to fallback to read-only mount, but the fill_super() operation returns EROFS in this case instead of returning success with read-only mount flag, so mount fails when encoutering directory or whiteout index entries. Bless this behavior by returning -EINVAL on directory and whiteout index entries as we do for all unsupported index entries. Fixes: 61b674710cd9 ("ovl: do not cleanup directory and whiteout index..") Cc: <stable@vger.kernel.org> # v4.13 Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Diffstat (limited to 'samples/vfio-mdev')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud