On Thu, Nov 24, 2016 at 10:46:35AM +0100, Jan Kara wrote:
> Currently ->iomap_begin() handler is called with entry lock held. If the
> filesystem held any locks between ->iomap_begin() and ->iomap_end()
> (such as ext4 which will want to hold transaction open), this would cause
> lock inversion with the iomap_apply() from standard IO path which first
> calls ->iomap_begin() and only then calls ->actor() callback which grabs
> entry locks for DAX.
I don't see the dax_iomap_actor() grabbing any entry locks for DAX? Is this
an issue currently, or are you just trying to make the code consistent so we
don't run into issues in the future?
Linux-nvdimm mailing list