Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Fixing swap1_stop
In article <C32A9472-EFC7-438D-B7F8-F806242C1745%eis.cs.tu-bs.de@localhost>,
J. Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost> wrote:
>
>> On 19. Aug 2017, at 14:20, Christos Zoulas <christos%zoulas.com@localhost> wrote:
>>
>> On Aug 19, 1:04pm, hannken%eis.cs.tu-bs.de@localhost ("J. Hannken-Illjes") wrote:
>> -- Subject: Re: Fixing swap1_stop
>>
>> | A long time ago forced unmounts tried to change open block device nodes
>> | to anonymous (not attached to a file system) nodes. This was racy and
>> | has been removed.
>> |
>> | With the recent changes to the VFS subsystem it should be possible to
>> | bring this behaviour back and instead of destroying open device nodes
>> | a forced unmount would detach them from the file system and keep them
>> | active.
>> |
>> | Did you mean something like this?
>>
>> Yes exactly that.
>
>Committed and pullup to -8 requested:
>
>src/sys/kern/vfs_vnode.c r1.97, r1.98
>src/sys/miscfs/deadfs/dead_vfsops.c r1.8
>src/sys/kern/vfs_mount.c r1.67
>src/sys/sys/vnode_impl.h r1.16
Excellent, so now swap1_stop works as is :-)
Many thanks,
christos
Home |
Main Index |
Thread Index |
Old Index