From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4854C56202 for ; Thu, 26 Nov 2020 03:14:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7145D216C4 for ; Thu, 26 Nov 2020 03:14:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="cV86WqIE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732389AbgKZDOM (ORCPT ); Wed, 25 Nov 2020 22:14:12 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:58911 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730696AbgKZDOK (ORCPT ); Wed, 25 Nov 2020 22:14:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606360449; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CP+P72YDkk6r+96+ukHLMOpDWmwuEuxrRgqlxfsqF6M=; b=cV86WqIEAGx49ylqPPO/phqvjyVUc84U9XDFL6hmB3wqLud2hITOUdGuZcTl0iZxhI5tI8 NEfmKxtxfG9WDYt9uLsnldj6vEBDSOA6P8lGsHWzbkpLLW6AMiGRRvhgHxYEBWdu5kto1J aEe8n6YqUEGBhSlKZLOZkfTnGtORrz8= Received: from mail-pl1-f199.google.com (mail-pl1-f199.google.com [209.85.214.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-575-Z-8UG9w3PGKbzTQaNlRKmg-1; Wed, 25 Nov 2020 22:14:07 -0500 X-MC-Unique: Z-8UG9w3PGKbzTQaNlRKmg-1 Received: by mail-pl1-f199.google.com with SMTP id bf9so591170plb.18 for ; Wed, 25 Nov 2020 19:14:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=CP+P72YDkk6r+96+ukHLMOpDWmwuEuxrRgqlxfsqF6M=; b=buVPbwwdW55B3Ymb6V7vd0/Ams+q5lP1+TU5gxblMPGSRFJfdYAY/ftfnhCY8Coi2d 3A//acARY03ZKnhVbX1h0vapl/Pd2SsoLXKbXtAcnzjAf15Po+u8fZXkmSRIlbg+Jz1X nC5Q2tnKqbshmqPMnyK5wvHFmM5oUYGF17J5wns1KrhkC5rqjHLkZjP04QVamBQrTQMz O7Kj301lTiy9t84IGG1YieNrmMeFmbyeiuC5IuEDK0ByqBs6QtWEj8vDWygNSMO1Wpsh /8p4fjXDJKNk+g9kJYDpulRVmLWVBJExwRXg2uSKgxZX77dkgKV87v+AOTu96MOknERM nP+g== X-Gm-Message-State: AOAM532h8sF7VX0Mz/mzF8qSEIXFsS6IUqwcbarP6m4ZTONqIb5ZkRQ0 hz+kMCbZjt+z7jqZS7WznlvD6AI3rdAvfZC3n9pecQ0gdYuYl4cG1Se0DOe/wPwLJ/SDPCh1v0R VQS3+O2vGzKGBY/hDKBLW X-Received: by 2002:a17:902:8209:b029:d6:d2c9:1db5 with SMTP id x9-20020a1709028209b02900d6d2c91db5mr1009626pln.54.1606360445890; Wed, 25 Nov 2020 19:14:05 -0800 (PST) X-Google-Smtp-Source: ABdhPJxsQ7WHZSGSQfaUiSHqtqqoRw0+46vwJE9kTOPMHu6GdPqgV+5NQiGJOmlZ+cstEeAN/7Af3A== X-Received: by 2002:a17:902:8209:b029:d6:d2c9:1db5 with SMTP id x9-20020a1709028209b02900d6d2c91db5mr1009611pln.54.1606360445702; Wed, 25 Nov 2020 19:14:05 -0800 (PST) Received: from xiangao.remote.csb ([209.132.188.80]) by smtp.gmail.com with ESMTPSA id k4sm2992384pfg.174.2020.11.25.19.14.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Nov 2020 19:14:05 -0800 (PST) Date: Thu, 26 Nov 2020 11:13:54 +0800 From: Gao Xiang To: Qinglang Miao Cc: Eric Sandeen , "Darrick J. Wong" , linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] xfs: check the return value of krealloc() in xfs_uuid_mount Message-ID: <20201126031354.GA345905@xiangao.remote.csb> References: <20201125065036.154312-1-miaoqinglang@huawei.com> <365b952c-7fea-3bc2-55ea-3f6b1c9f9142@sandeen.net> <9f998a9d-0684-6b45-009e-acf2e0ac4c85@huawei.com> <20201126021622.GA336866@xiangao.remote.csb> <5d6b6f6f-4bc3-2821-d5b1-569afba0221a@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5d6b6f6f-4bc3-2821-d5b1-569afba0221a@huawei.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Thu, Nov 26, 2020 at 11:05:03AM +0800, Qinglang Miao wrote: ... > > > > I'm not sure if Hulk CI is completely broken or not on this, also if > > such CI can now generate trivial patch (?) since the subject, commit > > message and even the variable name is quite similiar to > > https://lore.kernel.org/linux-xfs/20201124104531.561-2-thunder.leizhen@huawei.com > > in a day. > > > > And it'd be better to look into the code before sending patches... > Yeah.. I should pay more attension. Yeah, it'd be better to address/fix the Hulk CI false report if possible, so it won't have such warning in the future. Thanks, Gao Xiang > > > > Thanks, > > Gao Xiang > > Thanks for your advice~ > > > > > > Thanks for your adviceļ¼ > > > > > > > . > > >