Re: Locking strategy for device deletion (also see PR kern/48536)

To: Paul Goyette <paul%whooppee.com@localhost>
Subject: Re: Locking strategy for device deletion (also see PR kern/48536)
From: Taylor R Campbell <campbell+netbsd-tech-kern%mumble.net@localhost>
Date: Tue, 7 Jun 2016 19:31:28 +0000

   Date: Tue, 7 Jun 2016 18:28:11 +0800 (PHT)
   From: Paul Goyette <paul%whooppee.com@localhost>

   Can anyone suggest a reliable way to ensure that a device-driver module 
   can be _really_ safely detached?

General approach:

1. Prevent new references (e.g., devsw_detach).

2. Wait for existing references to drain (or roll back with
devsw_attach if you don't want to wait, and fail with EBUSY).

3. Unload.

Follow-Ups:
- Re: Locking strategy for device deletion (also see PR kern/48536)
  - From: Paul Goyette

References:
- Locking strategy for device deletion (also see PR kern/48536)
  - From: Paul Goyette

Prev by Date: re: Locking strategy for device deletion (also see PR kern/48536)
Next by Date: Re: /dev/sdN -> /dev/sdN[cd] (was: port-amd64/51216: Can't create wedges on a large (3TB) disk, gpt is ok but dkctl gives an error message)
Previous by Thread: re: Locking strategy for device deletion (also see PR kern/48536)
Next by Thread: Re: Locking strategy for device deletion (also see PR kern/48536)
Indexes:

Home | Main Index | Thread Index | Old Index