Received: by 2002:a5d:9c59:0:0:0:0:0 with SMTP id 25csp110622iof; Sun, 5 Jun 2022 22:42:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzrF2WCAq4U93o+DjbnAdfYpFIOk5vMaNSUkvpkhAhkbcJ10bG7hoqI4Ph3MF/MupUJw0Aq X-Received: by 2002:a05:6a00:170c:b0:51b:f057:85c2 with SMTP id h12-20020a056a00170c00b0051bf05785c2mr11903394pfc.18.1654494146331; Sun, 05 Jun 2022 22:42:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654494146; cv=none; d=google.com; s=arc-20160816; b=TYUROZYKgB1ED2nueWWFfQlRqCBdEK0Lx+y2T2+P84UhAQnHD8lwNLw5u4KP/AtGwR A9Mux/9TTw6rkIkHQey5dgdnb5YrsC/UTidtObIRN3BoLJcM8ZK1DSl9pgL/87QvRPK+ aWlg1e0G2p1S2kdjgZME++1FTyOzb/67p1pgTKU4SXBdGeWMrujj1NWN8IC2jDHHK+NL X79oDpK9cmY1N8+66RnjYbwVM6onfw2t7GuNsqaOHJ6gs8yv3MP1PVEV9lT6t9bWz0fc 0Wp1M/waYUzIODR91d3yFXkAkNu2vdJIWwqPNUAxJw4sOXe687hoHZqAoK5B5On+fBxh TNaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:subject:user-agent:mime-version:date:message-id; bh=5f8jGtteIWwgd7iJ6TixUyANCCCjSnmQMWMt8+/XQ0g=; b=Sq3EFipZxQLFiUawCASjg45MV5ihHb9D/UlmT60JhdmEfCwKqbbmh+aoNqiBjhuGGW QPt3wejlL5dg9B41MmAiZN+uX6RZaeZZ6n9WGf3AMZdCxFXz2R58gwZPbuXPqZnQjlBZ 1n9aXrQ52mBpvGbs6/6f9wLNjnbDff5SzpPfbuxNGZ75wdo3Hr74rWMFSoc0hb3Hwa74 ZuMH2vx82Z6HCZrFgHnjdyzpkLYgnMMajUK9sobVWpUtc/pQpAbKxiO0usXFJLx8QJI3 kyXVwKYrhOcFo219ThjLapmM6Y6zUGOXg9H5JUaOj4FhqkTLzNxcUlQIn/+6yn0thQYq 3lZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id e7-20020a656bc7000000b003fd2f71f2bfsi13461002pgw.585.2022.06.05.22.42.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Jun 2022 22:42:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id AFA4121DA2B; Sun, 5 Jun 2022 21:33:19 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351968AbiFFBeT (ORCPT + 99 others); Sun, 5 Jun 2022 21:34:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348931AbiFFBeR (ORCPT ); Sun, 5 Jun 2022 21:34:17 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E525222293 for ; Sun, 5 Jun 2022 18:34:15 -0700 (PDT) Received: from dggpemm500021.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4LGbbf6K6DzjXLj; Mon, 6 Jun 2022 09:33:18 +0800 (CST) Received: from dggpemm500002.china.huawei.com (7.185.36.229) by dggpemm500021.china.huawei.com (7.185.36.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 6 Jun 2022 09:34:14 +0800 Received: from [10.174.178.178] (10.174.178.178) by dggpemm500002.china.huawei.com (7.185.36.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 6 Jun 2022 09:34:13 +0800 Message-ID: Date: Mon, 6 Jun 2022 09:34:13 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.0.3 Subject: Re: [PATCH v2 1/3] mm/shmem: check return value of shmem_init_inodecache To: Matthew Wilcox CC: , , , , , References: <20220605035557.3957759-1-chenwandun@huawei.com> <20220605035557.3957759-2-chenwandun@huawei.com> From: Chen Wandun In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.178.178] X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To dggpemm500002.china.huawei.com (7.185.36.229) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/6/5 19:49, Matthew Wilcox wrote: > On Sun, Jun 05, 2022 at 11:55:55AM +0800, Chen Wandun wrote: >> It will result in null pointer access if shmem_init_inodecache fail, >> so check return value of shmem_init_inodecache > You ignored my suggestion from v1. Here, let me write it out for you. Hi Matthew, I didn't ignore your suggestion,  some explanation is needed, sorry for that. In V1, Kefeng point: "kmem_cache_create return a pointer to the cache on success, NULL on failure, so error = -ENOMEM; is right :)" so, I look some similar code such as init_inodecache in kinds of file system,  they all return -ENOMEM on failure, so is it OK to return -ENOMEM on failure :) Besides,  kmem_cache_create return NULL on failure, maybe returning error code on failure is more proper, but it is another job. > > +static int shmem_init_inodecache(void) > { > shmem_inode_cachep = kmem_cache_create("shmem_inode_cache", > sizeof(struct shmem_inode_info), > 0, SLAB_PANIC|SLAB_ACCOUNT, shmem_init_inode); > + if (!shmem_inode_cachep) > + return -ENOMEM; > + return 0; > } > > ... > > + error = shmem_init_inodecache(); > + if (error) > + goto out2; > > > .