DAX_ZERO_ENTRY is no longer the bit for zero entries - XA_ZERO_ENTRY is. The documentation above should be accurate to the definitions used accordingly. Signed-off-by: Amy Parker <enbyamy@xxxxxxxxx> --- fs/dax.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/fs/dax.c b/fs/dax.c index c2bdccef3140..ec23a4f9edd5 100644 --- a/fs/dax.c +++ b/fs/dax.c @@ -66,13 +66,13 @@ fs_initcall(init_dax_wait_table); /* * DAX pagecache entries use XArray value entries so they can't be mistaken - * for pages. We use one bit for locking, one bit for the entry size (PMD) - * and two more to tell us if the entry is a zero page or an empty entry that - * is just used for locking. In total four special bits. + * for pages. We use one bit for locking, one bit for the entry size (PMD), + * and one to tell if the entry is an empty entry just for locking. We use + * XArray's ZERO_ENTRY to tell us if the entry is a zero page. * - * If the PMD bit isn't set the entry has size PAGE_SIZE, and if the ZERO_PAGE - * and EMPTY bits aren't set the entry is a normal DAX entry with a filesystem - * block allocation. + * If the PMD bit isn't set the entry has size PAGE_SIZE, and if the EMPTY + * and ZERO_ENTRY bits aren't set the entry is a normal DAX entry with a + * filesystem block allocation. */ #define DAX_SHIFT (4) #define DAX_LOCKED (1UL << 0) -- 2.29.2
