Bug 216380 - mv /[dir == mountpoint] causes kernel panic
Summary: mv /[dir == mountpoint] causes kernel panic
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-22 19:07 UTC by rick
Modified: 2019-01-21 19:26 UTC (History)
3 users (show)

See Also:

Attachments
vbox screenshot (7.15 KB, image/png)
2017-01-22 19:07 UTC, rick 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rick 2017-01-22 19:07:07 UTC 
Created attachment 179223 [details]
vbox screenshot

Playback:
# zfs create zroot/test
# mv /test /home/testdir
-> panic

also in UFS, if the mv arguments coincide with mountpoints

# uname -a
FreeBSD 12.0-CURRENT #0 r311461: Thu Jan 5 22:46:38 UTC 2017  root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
Comment 1 commit-hook freebsd_committer freebsd_triage 2017-01-22 19:37:05 UTC 
A commit references this bug:

Author: kib
Date: Sun Jan 22 19:36:02 UTC 2017
New revision: 312645
URL: https://svnweb.freebsd.org/changeset/base/312645

Log:
  Provide fallback VOP methods for crossmp vnode.

  In particular, crossmp vnode might leak into rename code.

  PR:	216380
  Reported by:	fnacl@protonmail.com
  Sponsored by:	The FreeBSD Foundation
  X-MFC with:	r309425

Changes:
  head/sys/kern/vfs_lookup.c
Comment 2 commit-hook freebsd_committer freebsd_triage 2017-01-30 11:46:46 UTC 
A commit references this bug:

Author: pho
Date: Mon Jan 30 11:46:06 UTC 2017
New revision: 312985
URL: https://svnweb.freebsd.org/changeset/base/312985

Log:
  Added a regression test.

  PR:		216380
  Sponsored by:	Dell EMC Isilon

Changes:
  user/pho/stress2/misc/rename13.sh
Comment 3 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2019-01-21 19:26:45 UTC 
There is a commit referencing this PR, but it's still not closed and has been inactive for some time. Closing the PR as fixed but feel free to re-open it if the issue hasn't been completely resolved.

Thanks