[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F21CA16.3020002@ubuntu.com>
Date: Thu, 26 Jan 2012 16:48:06 -0500
From: Phillip Susi <psusi@...ntu.com>
To: Vivek Goyal <vgoyal@...hat.com>
CC: Maxim Patlasov <maxim.patlasov@...il.com>, joe@...ches.com,
kzak@...hat.com, linux-kernel@...r.kernel.org, jaxboe@...ionio.com
Subject: Re: [PATCH 1/2] Add partition resize function to BLKPG ioctl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/26/2012 4:04 PM, Vivek Goyal wrote:
>> Another idea that I had but have not yet checked to see if it is
>> actually feasible is to copy the struct genhd, change the size
>> of the copy, and replace the existing one since updating the
>> pointer will be atomic.
>
> You will run into issues if somebody has a pointer stored to
> genhd.
They are already kept in an RCU list which has the same problem.
Doesn't that deal with it by using reference counters, so the reader
can keep and use the pointer to the old structure just fine, and it
will be cleaned up when they release the reference.
> I think simpler thing would be to stick with sequence counter
> approach which keeps read side lockless. We can fix other writers
> of nr_sects over a period of time. If nobody has complained so
> far, that means we don't run into issues frequently and it is not a
> huge concern.
So you think the patch is fine the way it is?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPIcoWAAoJEJrBOlT6nu75SfYIALuzdfVKVKBdXa16nrKj4XtU
T2PHkbNRRJhFjRbtxfyLkAWL//yEz4S1z08z+RCpP8YcuQ47bKa8WnoamTYSkzuV
SLjKjjec5a2v/SpEBl6QSHUxg73kBXi0pvsQDEm1+j0ZinZk7Sy+x2uZ8fKwYYYp
Z8dOShzSR5toIdpi42SbgmtO/qrdqbRcxANvCVwtybeAyVqmIiOY4DTdBm4YhTp5
GeVTUYTsfjuS3P+i1JJaVmUPMtMzOegXLKI775gWTn+x90TIMnoI+lXa2h1QeZOL
ZCsk6x7BF9t3lAkk60E8BePFFGoYpz3rHrAsco2qizrXz4Z0WVlh6KGIad0xDF4=
=SifF
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists