[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH] improve atomicity of device creation
- From: Alasdair G Kergon <agk redhat com>
- To: Kay Sievers <kay sievers vrfy org>
- Cc: device-mapper development <dm-devel redhat com>, linux-hotplug-devel lists sourceforge net
- Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation
- Date: Tue, 11 Dec 2007 18:08:29 +0000
On Tue, Dec 11, 2007 at 06:51:31PM +0100, Kay Sievers wrote:
> We can make the kernel's kobject_uevent() return the generated seqnum to
> the caller.
Is 32 bits enough?
We added 'uint32_t padding;' recently which we I reckon we could now use for
this.
dm_kobject_uevent() and alloc_dev() could keep a new field in
struct mapped_device up-to-date, and a new function could return its
value to dm-ioctl.c code to place into a renamed 'padding' field
before returning to userspace?
Alasdair
--
agk redhat com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]