Searched hist:bccece1ead368149f90e05ad104dfbfda4422f5d (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/overlayfs/ |
| H A D | util.c | diff bccece1ead368149f90e05ad104dfbfda4422f5d Tue Mar 17 09:04:22 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> ovl: allow remote upper
No reason to prevent upper layer being a remote filesystem. Do the
revalidation in that case, just as we already do for lower layers.
This lets virtiofs be used as upper layer, which appears to be a real use
case.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
| H A D | namei.c | diff bccece1ead368149f90e05ad104dfbfda4422f5d Tue Mar 17 09:04:22 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> ovl: allow remote upper
No reason to prevent upper layer being a remote filesystem. Do the
revalidation in that case, just as we already do for lower layers.
This lets virtiofs be used as upper layer, which appears to be a real use
case.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
| H A D | super.c | diff bccece1ead368149f90e05ad104dfbfda4422f5d Tue Mar 17 09:04:22 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> ovl: allow remote upper
No reason to prevent upper layer being a remote filesystem. Do the
revalidation in that case, just as we already do for lower layers.
This lets virtiofs be used as upper layer, which appears to be a real use
case.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|