aboutsummaryrefslogtreecommitdiff
path: root/sbin/savecore/tests/(public-mirror)
diff options
context:
space:
mode:
authorJason A. Harmening <jah@FreeBSD.org>2025-11-29 07:53:16 +0000
committerJason A. Harmening <jah@FreeBSD.org>2025-12-12 06:32:05 +0000
commit0247b4018de2c341ac59a585362c10044cea86ad (patch)
tree2946c3c05c97abb6bf1817ff1062a68964702bbd /sbin/savecore/tests/(public-mirror)
parent5c025978fc3649730329994eecc56ada119e6717 (diff)
unionfs: detect common deadlock-producing mount misconfigurationsHEADmain
When creating a unionfs mount, it's fairly easy to shoot oneself in the foot by specifying upper and lower file hierarchies that resolve back to the same vnodes. This is fairly easy to do if the sameness is not obvious due to aliasing through nullfs or other unionfs mounts (as in the associated PR), and will produce either deadlock or failed locking assertions on any attempt to use the resulting unionfs mount. Leverage VOP_GETLOWVNODE() to detect the most common cases of foot-shooting at mount time and fail the mount with EDEADLK. This is not meant to be an exhaustive check for all possible deadlock-producing scenarios, but it is an extremely cheap and simple approach that, unlike previous proposed fixes, also works in the presence of nullfs aliases. PR: 172334 Reported by: ngie, Karlo Miličević <karlo98.m@gmail.com> Reviewed by: kib, olce Tested by: pho MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D53988
Diffstat (limited to 'sbin/savecore/tests/(public-mirror)')
0 files changed, 0 insertions, 0 deletions