On Mon, Dec 30, 2019 at 3:14 PM Amir Goldstein <amir73il@xxxxxxxxx> wrote:
>
> Also test that d_ino of readdir entries and i_ino from /proc/locks are
> consistent with st_ino and that inode numbers persist after rename to
> new parent, drop caches and mount cycle.
overlay/070 and overlay/071 fail for me like this:
QA output created by 071
+flock: cannot open lock file
/scratch/ovl-mnt/lowertestdir/blkdev: No such device or address
...
I.e. there's no block dev with rdev=1/1.
I don't see any other way to fix this, than to remove the device
tests. Why are these needed? Is locking code in any way dependent on
file type?
Thanks,
Miklos
