In message <[EMAIL PROTECTED]>,Russ Allbery writes: > > BUG_ON(victim->d_parent->d_inode != dir); >
this mountpoint wouldn't happen to be mounted multiple times would it? this really upsets the linux fs stack. it doesnt like afs directories that are mounted in multiple places (lookup does a bit of work to prevent directory dentries getting multiple "aliases") since this can deadlock when locking directories apparently (as i recall). i could see a problem if you lookup the mountpoint first in different parent dir, then you move it from a different directory to a new directory, the mountpoint's parent is not going to be the directory its currently in. i cant seem to duplicate this though. i think check_bad_parent() should catch this (except for when the parent volid dont change). what afs version are you running? can you be more specific about duplicating this problem? _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
