From: Chao Yu <yuchao0@huawei.com>
To: fengyubo <fengyubo3@huawei.com>, <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: lost matching-pair of trace in f2fs_truncate_inode_blocks
Date: Sat, 20 Jun 2020 17:35:53 +0800 [thread overview]
Message-ID: <db36eb3c-9c27-f5dd-e390-5f5a6f5da2f4@huawei.com> (raw)
In-Reply-To: <1592642383-140667-1-git-send-email-fengyubo3@huawei.com>
On 2020/6/20 16:39, fengyubo wrote:
> From: Yubo Feng <fengyubo3@huawei.com>
>
> if get_node_path() return -E2BIG and trace of
> f2fs_truncate_inode_blocks_enter/exit enabled
> then the matching-pair of trace_exit will lost
> in log.
>
> Signed-off-by: Yubo Feng <fengyubo3@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-06-20 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 8:39 [f2fs-dev] [PATCH v1] f2fs: lost matching-pair of trace in f2fs_truncate_inode_blocks fengyubo
2020-06-20 9:35 ` Chao Yu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db36eb3c-9c27-f5dd-e390-5f5a6f5da2f4@huawei.com \
--to=yuchao0@huawei.com \
--cc=fengyubo3@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).