Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4427471ybi; Mon, 27 May 2019 18:24:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqwcPcsFjuxNYmnJW3D2pZJ3q2ekw4p+4kwGyKVcjrkANEH8l7eF9srfvb9f7dutjE35jOKV X-Received: by 2002:a63:d00d:: with SMTP id z13mr32495183pgf.368.1559006692794; Mon, 27 May 2019 18:24:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559006692; cv=none; d=google.com; s=arc-20160816; b=HbIknU0OQUC/xpcVVAYPshdtxXmmBAq0SY8GBzAHqlbl/oo1dPxvzK6jDehqxKG1hN 0lLT3r9pMIQO66AFfhsALXXa4SpHdH8DHmd+m4Yvy4DvWDmGzz0aOf7eIWqortKi+Ddj OGia4XC5lWK2EhPmowNTuMnM+d8JLIrU+2u1aUR5lsPvDxJ6f04wRK3WtiR6afeUToht yyael9F2RymV82VOKyrrtRSEoiHj0TCIl0CzyXX0mXUOl1i/8Vnh+7i5HbVLNTMjHn/A OF53EdKB2Ozb3PcF+pWABx1hIuKudpSIW/dsR9bvWnGjQViwpY69jbJ3Y3zlLp4ccxzA 4gbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=kF1mlz899e85Am9gzYVqBx4SVroqLqMerczQ6T0Yf34=; b=mrgxq9+yTHSwL7QDBEZEabO9zO+DQjul24JsedTxjHvogeswItNWHDWqPAE8bRHoYN C/hXxV1RQCDFKzf8JeyjeLDUir0bxn79u8MBSIEWjSynEsb0+l/6fWwxpTrWGy5v0/j4 07qg9Cy+tUNWca/+CSk8leq6CrJaQQYYzgWfX44tx95tmxUzT8ruDH1GKC3PnLytEd/i kw1Hzf9GqoOjgFli7CcaotieOZnS0iUvgHdsZtGkOmLYSVilEIw+HsZlFuEAUPOTo6RV R1um1Ej+ncsEAkNh9qlPCNkExJtl/X9LwtflnfN8EpMx4680Zwqpe+fiej4y8MuGwciL bv1A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b7si21657520pgk.553.2019.05.27.18.24.37; Mon, 27 May 2019 18:24:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727775AbfE1BXC (ORCPT + 99 others); Mon, 27 May 2019 21:23:02 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:54346 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727090AbfE1BXC (ORCPT ); Mon, 27 May 2019 21:23:02 -0400 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 6612BE665F8B3F37B701; Tue, 28 May 2019 09:22:59 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.211) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 28 May 2019 09:22:55 +0800 Subject: Re: [PATCH v2] f2fs: ratelimit recovery messages To: Sahitya Tummala , Jaegeuk Kim , CC: References: <1558962655-25994-1-git-send-email-stummala@codeaurora.org> From: Chao Yu Message-ID: <94025a6d-f485-3811-5521-ed5c9b4d1d77@huawei.com> Date: Tue, 28 May 2019 09:23:15 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1558962655-25994-1-git-send-email-stummala@codeaurora.org> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sahitya, On 2019/5/27 21:10, Sahitya Tummala wrote: > Ratelimit the recovery logs, which are expected in case > of sudden power down and which could result into too > many prints. FYI https://lore.kernel.org/patchwork/patch/973837/ IMO, we need those logs to provide evidence during trouble-shooting of file data corruption or file missing problem... So I suggest we can keep log as it is in recover_dentry/recover_inode, and for the log in do_recover_data, we can record recovery info [isize_kept, recovered_count, err ...] into struct fsync_inode_entry, and print them in batch, how do you think? Thanks, > > Signed-off-by: Sahitya Tummala > --- > v2: > - fix minor formatting and add new line for printk > > fs/f2fs/recovery.c | 18 +++++++++--------- > 1 file changed, 9 insertions(+), 9 deletions(-) > > diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c > index e04f82b..60d7652 100644 > --- a/fs/f2fs/recovery.c > +++ b/fs/f2fs/recovery.c > @@ -188,8 +188,8 @@ static int recover_dentry(struct inode *inode, struct page *ipage, > name = ""; > else > name = raw_inode->i_name; > - f2fs_msg(inode->i_sb, KERN_NOTICE, > - "%s: ino = %x, name = %s, dir = %lx, err = %d", > + printk_ratelimited(KERN_NOTICE > + "%s: ino = %x, name = %s, dir = %lx, err = %d\n", > __func__, ino_of_node(ipage), name, > IS_ERR(dir) ? 0 : dir->i_ino, err); > return err; > @@ -292,8 +292,8 @@ static int recover_inode(struct inode *inode, struct page *page) > else > name = F2FS_INODE(page)->i_name; > > - f2fs_msg(inode->i_sb, KERN_NOTICE, > - "recover_inode: ino = %x, name = %s, inline = %x", > + printk_ratelimited(KERN_NOTICE > + "recover_inode: ino = %x, name = %s, inline = %x\n", > ino_of_node(page), name, raw->i_inline); > return 0; > } > @@ -642,11 +642,11 @@ static int do_recover_data(struct f2fs_sb_info *sbi, struct inode *inode, > err: > f2fs_put_dnode(&dn); > out: > - f2fs_msg(sbi->sb, KERN_NOTICE, > - "recover_data: ino = %lx (i_size: %s) recovered = %d, err = %d", > - inode->i_ino, > - file_keep_isize(inode) ? "keep" : "recover", > - recovered, err); > + printk_ratelimited(KERN_NOTICE > + "recover_data: ino = %lx (i_size: %s) recovered = %d, err = %d\n", > + inode->i_ino, > + file_keep_isize(inode) ? "keep" : "recover", > + recovered, err); > return err; > } > >