Received: by 10.223.185.116 with SMTP id b49csp6128123wrg; Wed, 28 Feb 2018 04:35:08 -0800 (PST) X-Google-Smtp-Source: AH8x226HyQlu0IPsPOuC/vbv/R5v9XFJOh/6bYWwO4KXY1ke9GXalGkMMey4/y7NwvZIeitAFgL4 X-Received: by 10.99.120.138 with SMTP id t132mr13990364pgc.54.1519821308245; Wed, 28 Feb 2018 04:35:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519821308; cv=none; d=google.com; s=arc-20160816; b=xg+ZZ/jEQxThkSBL3AHz6fxJ0wU/dQJFr/ipoWTzMKYUBiK87Di6NGSUVMzqeOAia7 eaAIew3KYs+b52kOxU2ZuduJ6E6NbxY7Lj0np6+zl594jkkugfSJXsgfVAAWvYwsnAFh N5A3AcxztowFR0Bff7jpMTPg/ZejKjfSukGP48NgTrpbjD1lMFTdhO91cEY0HmKKYU/q 2KrcEmbmXc2wP+cflZpTz2kAswJuON1HG9q5ovjVYfKSidKTm+xuFw/Qb9tLH5cKayN4 0Fqz/4xbkc+n1n7846uuEsaxCVFOGHA/8co4AVSNl79Q3XCsmJuAYlEnLCEcEmx4D0X4 wK5g== 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:arc-authentication-results; bh=C9h7o9FPtmwncJnHJQRcmMws8s5Ee0rvW2NaQHeB49I=; b=zKr9Wk5iyJ1voUHwVhm+oWaQo3Z+di0cY5Nv+1/lt4s3l6pX0tZDZjnN/AUvxiW8x+ dgzdbEooYz9CxrYgI5eENFNVpQDI/RPxcThswNlnv1DLLfp+VM56+Y7SK/BqlIuMkrUC LInGPKmFJ3CNJv8CZ9qd+R7vG3SY6g5ddjKz2lhd7SY/n1DwzOuskcMgck3UkZuqrU8H y6R1X18nEJmAVNgUeaqj2EEY27+agFq4sVUUyCXtNu77w+RUyqZS0aBh5mcXjXmYJsMT WWhQNKUQOE3nLCalA7+MxQ2gTQsAxpplI4pY7+vL4k9jhCCSQUHDepYOxuEsfI1RozwE 3hAQ== 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 e3si975234pgv.79.2018.02.28.04.34.51; Wed, 28 Feb 2018 04:35:08 -0800 (PST) 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 S1752503AbeB1Md7 (ORCPT + 99 others); Wed, 28 Feb 2018 07:33:59 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:5720 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752195AbeB1Md6 (ORCPT ); Wed, 28 Feb 2018 07:33:58 -0500 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id C4640BF31D0A; Wed, 28 Feb 2018 20:33:44 +0800 (CST) Received: from [127.0.0.1] (10.111.220.140) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.361.1; Wed, 28 Feb 2018 20:33:36 +0800 Subject: Re: [PATCH v4] Revert "f2fs crypto: avoid unneeded memory allocation in ->readdir" To: Jaegeuk Kim CC: , , , , , , , , References: <1519463698-60555-1-git-send-email-yunlong.song@huawei.com> <1519787857-107910-1-git-send-email-yunlong.song@huawei.com> <20180228054810.GB86647@jaegeuk-macbookpro.roam.corp.google.com> From: Yunlong Song Message-ID: <0a7fec6b-0f94-00f7-f5d4-8eac1f9cee73@huawei.com> Date: Wed, 28 Feb 2018 20:32:20 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20180228054810.GB86647@jaegeuk-macbookpro.roam.corp.google.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.111.220.140] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.