Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp9343084rwi; Tue, 25 Oct 2022 19:00:42 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6iyv5cO1rSA76uiph9x3QpAS3EBNDcH0HI+ytAnC/J1RZZ2VBnpfYgGFM9hdY8Jnbp4I/g X-Received: by 2002:a05:6a00:1306:b0:555:6d3f:11ed with SMTP id j6-20020a056a00130600b005556d3f11edmr41786083pfu.55.1666749642284; Tue, 25 Oct 2022 19:00:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666749642; cv=none; d=google.com; s=arc-20160816; b=Vx9IUH58ZoCe+wXNYNZYjxbfwD08m9OTBgazXTjy6c8AJ1WeEZOmAe9QzCEPSsU/QJ tTJUd8bjoiQQ8WfZTUy5axrSOY6Nnn2EvWKOn/POj5Oq4W1BbAiOIhmm4zH5jasNznf4 Jn0EV5Od5ikxAgn+zoVPOCjzaXvtSL2HMVmPk5FY51H1gLYS78F6aJMw+/kXtxtDiPtj jACUDhrrmjC8nUTLz8NrhTjjI3brCGmPG+PlXMAlY9trJws3dapbypVGETI9pR7Gcwdk 4JkTI4d/IA8WK7ekV8641q+w4gaItvObFqxGZn1y2BIil08Z3WSaMPzvg9kXGc+ZUslv ZY5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from; bh=CmnGB8Ef9xIBgvOIYcA1q+YLYrkt8iiGUsnzYQspaWM=; b=uMbspibUWaVCHXKPn4AfW7v4LILuYV/o2vIi7C9jXuMEa3fqCnePWlRvTq49PcwigS e9Am6M9/09zsquDLMjME6KmYSvoos9i0aB9Aov8JMUGAlPX2c1WkDbBWamn9uRQcPA5E JPfNxdBwDBvTLngiPpjLH0rm1kobMU7KnXtlJS9zBjuenUosQ+xGxstvhpTNiGU5u5vD Peo8skMAGpfX8YkzqbbrgyVyTie6/j9gFS9EJslnPSXKU5CrNx2W+w+jlfBTTKCpTXLd sYtnQgutaq4K5Y2y+/Yi/T+0WWuYKqpCELzNibxk91bu1qXiZlYWn1fGEC6nlPRuk/mf 7Xpw== 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:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 142-20020a630094000000b0046edf48afefsi4774463pga.608.2022.10.25.19.00.03; Tue, 25 Oct 2022 19:00:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232380AbiJZBgW (ORCPT + 99 others); Tue, 25 Oct 2022 21:36:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230428AbiJZBgT (ORCPT ); Tue, 25 Oct 2022 21:36:19 -0400 Received: from mail.nfschina.com (unknown [124.16.136.209]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id F0D136A514; Tue, 25 Oct 2022 18:36:18 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by mail.nfschina.com (Postfix) with ESMTP id AD1D31E80C9B; Wed, 26 Oct 2022 09:34:52 +0800 (CST) X-Virus-Scanned: amavisd-new at test.com Received: from mail.nfschina.com ([127.0.0.1]) by localhost (mail.nfschina.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id No9tDtmXi6nw; Wed, 26 Oct 2022 09:34:50 +0800 (CST) Received: from localhost.localdomain (unknown [219.141.250.2]) (Authenticated sender: zeming@nfschina.com) by mail.nfschina.com (Postfix) with ESMTPA id CD88C1E80C8E; Wed, 26 Oct 2022 09:34:49 +0800 (CST) From: Li zeming To: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, Li zeming Subject: [PATCH v3] btrfs: volumes: Increase bioc pointer check Date: Wed, 26 Oct 2022 09:36:11 +0800 Message-Id: <20221026013611.2900-1-zeming@nfschina.com> X-Mailer: git-send-email 2.18.2 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham 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 The __GFP_NOFAIL flag will cause memory to be allocated an infinite number of times until the allocation is successful, but it is best to use it only for very necessary code, and try not to use it. The alloc_btrfs_io_context function looks a little closer to normal (excuse my analysis), but I think we can remove __GFP_NOFAIL from it and add a bioc pointer allocation check that returns NULL if the allocation fails. Signed-off-by: Li zeming --- v2: Add annotation vocabulary modify, remove __GFP_NOFAIL flag. v3: Modifying the Description. fs/btrfs/volumes.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index 064ab2a79c80..b8d901f58995 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -5891,7 +5891,9 @@ static struct btrfs_io_context *alloc_btrfs_io_context(struct btrfs_fs_info *fs_ * and the stripes. */ sizeof(u64) * (total_stripes), - GFP_NOFS|__GFP_NOFAIL); + GFP_NOFS); + if (!bioc) + return NULL; atomic_set(&bioc->error, 0); refcount_set(&bioc->refs, 1); @@ -6071,7 +6073,7 @@ struct btrfs_discard_stripe *btrfs_map_discard(struct btrfs_fs_info *fs_info, * array of stripes. * For READ, it also needs to be supported using the same mirror number. * - * If the requested block is not left of the left cursor, EIO is returned. This + * If the requested block is not left of the left cursor, EIO should be returned. This * can happen because btrfs_num_copies() returns one more in the dev-replace * case. */ -- 2.18.2