Re: [PATCH] btrfs: print message when tree-log replay starts

[David Sterba <dsterba@suse.cz>]

On Thu, Feb 06, 2020 at 11:48:28AM +0800, Anand Jain wrote:
> On 2/6/20 11:45 AM, Anand Jain wrote:
> > On 2/6/20 12:12 AM, David Sterba wrote:
> >> There's no logged information about tree-log replay although this is
> >> something that points to previous unclean unmount. Other filesystems
> >> report that as well.
> >>
> >> Suggested-by: Chris Murphy <lists@colorremedies.com>
> >> CC: stable@vger.kernel.org # 4.4+
> >> Signed-off-by: David Sterba <dsterba@suse.com>
> >> ---
> >>   fs/btrfs/disk-io.c | 1 +
> >>   1 file changed, 1 insertion(+)
> >>
> >> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> >> index 28622de9e642..295d5ebc9d5e 100644
> >> --- a/fs/btrfs/disk-io.c
> >> +++ b/fs/btrfs/disk-io.c
> >> @@ -3146,6 +3146,7 @@ int __cold open_ctree(struct super_block *sb,
> >>       /* do not make disk changes in broken FS or nologreplay is given */
> >>       if (btrfs_super_log_root(disk_super) != 0 &&
> >>           !btrfs_test_opt(fs_info, NOLOGREPLAY)) {
> 
> 
> >> +        btrfs_info("start tree-log replay");
> 
> btrfs_info() needs struct btrfs_fs_info as first arg.

Doh, that's what I get when I take months old patches and only briefly
review them before sending.