Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A569C64EC4 for ; Sat, 4 Mar 2023 10:18:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229721AbjCDKSY (ORCPT ); Sat, 4 Mar 2023 05:18:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229584AbjCDKSW (ORCPT ); Sat, 4 Mar 2023 05:18:22 -0500 Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B7CAE3B2 for ; Sat, 4 Mar 2023 02:18:21 -0800 (PST) Received: from kwepemm600012.china.huawei.com (unknown [172.30.72.57]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4PTLQH4gg6z1dy2C; Sat, 4 Mar 2023 18:18:15 +0800 (CST) Received: from [10.67.109.57] (10.67.109.57) by kwepemm600012.china.huawei.com (7.193.23.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Sat, 4 Mar 2023 18:18:18 +0800 Subject: Re: [PATCH v3] sched: pick_next_rt_entity(): check list_entry References: <8f5c938f-5c31-655b-fd8d-415fa192d705@huawei.com> To: Reply-To: <20230128-list-entry-null-check-sched-v3-1-b1a71bd1ac6b@diag.uniroma1.it> CC: , , , , , , , , , , , , , , , From: "guanjing (D)" Message-ID: Date: Sat, 4 Mar 2023 18:18:17 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.109.57] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemm600012.china.huawei.com (7.193.23.74) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, borrello: I wonder why you send this patch? Did you meet such a problem in a real-world scenario, or it is a static warning style? Thanks, Guanjin.