device-dax: fix dax_dev_huge_fault() unknown fault size handling
authorPushkar Jambhlekar <pushkar.iit@gmail.com>
Tue, 11 Apr 2017 16:12:25 +0000 (09:12 -0700)
committerDan Williams <dan.j.williams@intel.com>
Thu, 13 Apr 2017 04:59:13 +0000 (21:59 -0700)
commit54eafcc9e339affb8982fd21e1fc4aa4a036655b
tree07a660bb3a05894e2f44988f836d25509397c3fc
parentbfca9acf1a5df0ff98fbf47e363adb48612bb7ec
device-dax: fix dax_dev_huge_fault() unknown fault size handling

The default case for dax_dev_huge_fault() fault size handling mistakenly
returns when it should unlock. This is not a problem in practice since
the only three possible fault sizes are handled. Going forward, if the
core mm adds a new fault size beyond pte, pmd, or pud device-dax should
abort VM_FAULT_SIGBUS requests not VM_FAULT_FALLBACK since device-dax
guarantees a configured fault granularity for all faults.

Signed-off-by: Pushkar Jambhlekar <pushkar.iit@gmail.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/dax/dax.c