nilfs_attach_log_writer(): use ->bd_mapping->host instead of ->bd_inode
authorAl Viro <viro@zeniv.linux.org.uk>
Mon, 29 Apr 2024 00:39:55 +0000 (20:39 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Fri, 3 May 2024 06:36:55 +0000 (02:36 -0400)
I suspect that inode_attach_wb() use is rather unidiomatic, but
that's a separate story - in any case, its use is a few times
per mount *and* the route by which we access that inode is
"the host of address_space a page belongs to".

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/nilfs2/segment.c

index aa5290cb7467cf2d756ec042b41b57e30c4336ae..15188e79958021f385a7eedd18bc8f6f52446d13 100644 (file)
@@ -2790,7 +2790,7 @@ int nilfs_attach_log_writer(struct super_block *sb, struct nilfs_root *root)
        if (!nilfs->ns_writer)
                return -ENOMEM;
 
-       inode_attach_wb(nilfs->ns_bdev->bd_inode, NULL);
+       inode_attach_wb(nilfs->ns_bdev->bd_mapping->host, NULL);
 
        err = nilfs_segctor_start_thread(nilfs->ns_writer);
        if (unlikely(err))