NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/42210: rename EXDEV & abortop fail

>Number:         42210
>Category:       kern
>Synopsis:       rename EXDEV & abortop fail
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 21 19:30:00 +0000 2009
>Originator:     Antti Kantee
read it and weep inc.
In a new and exciting episode of "I thought we fixed the last bug
from rename last week", plenty of drivers will happily fail VOP_RENAME
with EXDEV but neglect to call VOP_ABORTOP.  Notably, since one of the
vnodes might be of completely different type, a given driver
cannot decide to just not call abortop because it "knows" it's
not required.

Is there some layering marvel preventing us from checking for
EXDEV before calling rename?  otherwise, have fun

Home | Main Index | Thread Index | Old Index