From: Yunlong Song <yunlong.song@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <chao@kernel.org>, <yuchao0@huawei.com>,
<yunlong.song@icloud.com>, <miaoxie@huawei.com>,
<bintian.wang@huawei.com>, <shengyong1@huawei.com>,
<heyunlei@huawei.com>, <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] Revert "f2fs crypto: avoid unneeded memory allocation in ->readdir"
Date: Wed, 28 Feb 2018 20:32:20 +0800 [thread overview]
Message-ID: <0a7fec6b-0f94-00f7-f5d4-8eac1f9cee73@huawei.com> (raw)
In-Reply-To: <20180228054810.GB86647@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/2/28 13:48, Jaegeuk Kim wrote:
> Hi Yunlong,
>
> As Eric pointed out, how do you think using nohighmem for directory likewise
> ext4, which looks like more efficient?
OK, I have sent out another patch like this.
Actually, we don't need to do this in
> most of recent kernels, right?
>
Why? I have got this panic using arm with recent kernel.
prev parent reply other threads:[~2018-02-28 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 9:14 [PATCH] f2fs: allocate buffer for decrypting filename to avoid panic Yunlong Song
2018-02-24 18:32 ` Eric Biggers
2018-02-26 3:06 ` Yunlong Song
2018-02-26 3:42 ` Chao Yu
2018-02-26 2:57 ` [PATCH v2] " Yunlong Song
2018-02-27 10:40 ` Chao Yu
2018-02-28 2:19 ` [PATCH v3] " Yunlong Song
2018-02-28 2:49 ` Chao Yu
2018-02-28 3:17 ` [PATCH v4] Revert "f2fs crypto: avoid unneeded memory allocation in ->readdir" Yunlong Song
2018-02-28 5:48 ` Jaegeuk Kim
2018-02-28 9:50 ` Chao Yu
2018-03-01 2:50 ` Jaegeuk Kim
2018-03-01 3:02 ` Chao Yu
2018-02-28 12:32 ` Yunlong Song [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=0a7fec6b-0f94-00f7-f5d4-8eac1f9cee73@huawei.com \
--to=yunlong.song@huawei.com \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=shengyong1@huawei.com \
--cc=yuchao0@huawei.com \
--cc=yunlong.song@icloud.com \
/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).