From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: use kvmalloc, if kmalloc is failed
Date: Tue, 18 Dec 2018 16:37:58 +0800 [thread overview]
Message-ID: <a56ea91f-892d-a663-d4f2-6da8b851ec22@huawei.com> (raw)
In-Reply-To: <20181214050127.45025-1-jaegeuk@kernel.org>
On 2018/12/14 13:01, Jaegeuk Kim wrote:
> One report says memalloc failure during mount.
>
> (unwind_backtrace) from [<c010cd4c>] (show_stack+0x10/0x14)
> (show_stack) from [<c049c6b8>] (dump_stack+0x8c/0xa0)
> (dump_stack) from [<c024fcf0>] (warn_alloc+0xc4/0x160)
> (warn_alloc) from [<c0250218>] (__alloc_pages_nodemask+0x3f4/0x10d0)
> (__alloc_pages_nodemask) from [<c0270450>] (kmalloc_order_trace+0x2c/0x120)
> (kmalloc_order_trace) from [<c03fa748>] (build_node_manager+0x35c/0x688)
> (build_node_manager) from [<c03de494>] (f2fs_fill_super+0xf0c/0x16cc)
> (f2fs_fill_super) from [<c02a5864>] (mount_bdev+0x15c/0x188)
> (mount_bdev) from [<c03da624>] (f2fs_mount+0x18/0x20)
> (f2fs_mount) from [<c02a68b8>] (mount_fs+0x158/0x19c)
> (mount_fs) from [<c02c3c9c>] (vfs_kern_mount+0x78/0x134)
> (vfs_kern_mount) from [<c02c76ac>] (do_mount+0x474/0xca4)
> (do_mount) from [<c02c8264>] (SyS_mount+0x94/0xbc)
> (SyS_mount) from [<c0108180>] (ret_fast_syscall+0x0/0x48)
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
prev parent reply other threads:[~2018-12-18 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 5:01 [PATCH 1/3] f2fs: use kvmalloc, if kmalloc is failed Jaegeuk Kim
2018-12-14 5:01 ` [PATCH 2/3] f2fs: correct wrong spelling, issing_* Jaegeuk Kim
2018-12-18 8:39 ` [f2fs-dev] " Chao Yu
2018-12-14 5:01 ` [PATCH 3/3] f2fs: flush stale issued discard candidates Jaegeuk Kim
2018-12-18 8:49 ` [f2fs-dev] " Chao Yu
2018-12-18 22:43 ` Jaegeuk Kim
2018-12-19 3:21 ` Chao Yu
2018-12-18 8:37 ` 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=a56ea91f-892d-a663-d4f2-6da8b851ec22@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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