Re: [PATCH 3/4] dax: Introduce alloc_dev_dax_id()

2023-06-16 Thread Ira Weiny
Dan Williams wrote: > Ira Weiny wrote: > > Dan Williams wrote: > > > The reference counting of dax_region objects is needlessly complicated, > > > has lead to confusion [1], and has hidden a bug [2]. Towards cleaning up > > > that mess introduce alloc_dev_dax_id() to minimize the holding of a > >

Re: [PATCH 3/4] dax: Introduce alloc_dev_dax_id()

2023-06-15 Thread Dan Williams
Ira Weiny wrote: > Dan Williams wrote: > > The reference counting of dax_region objects is needlessly complicated, > > has lead to confusion [1], and has hidden a bug [2]. Towards cleaning up > > that mess introduce alloc_dev_dax_id() to minimize the holding of a > > dax_region reference to only

Re: [PATCH 3/4] dax: Introduce alloc_dev_dax_id()

2023-06-03 Thread Ira Weiny
Dan Williams wrote: > The reference counting of dax_region objects is needlessly complicated, > has lead to confusion [1], and has hidden a bug [2]. Towards cleaning up > that mess introduce alloc_dev_dax_id() to minimize the holding of a > dax_region reference to only what dev_dax_release()

[PATCH 3/4] dax: Introduce alloc_dev_dax_id()

2023-06-03 Thread Dan Williams
The reference counting of dax_region objects is needlessly complicated, has lead to confusion [1], and has hidden a bug [2]. Towards cleaning up that mess introduce alloc_dev_dax_id() to minimize the holding of a dax_region reference to only what dev_dax_release() needs, the dax_region->ida. Part