Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp920692pxb; Tue, 29 Mar 2022 12:45:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxtS1sZXhus8HoHxI2krN+EajFRvHLA8Zzn82DoNprHUBroN0DX7EFAmI5uldMBNPuDF8Qq X-Received: by 2002:a17:902:e9d4:b0:153:bd06:859c with SMTP id 20-20020a170902e9d400b00153bd06859cmr31565814plk.8.1648583155327; Tue, 29 Mar 2022 12:45:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648583155; cv=none; d=google.com; s=arc-20160816; b=0PVE1bZXsYmlnZG/klDfAbb0TgMRORU2u9iSGvKFIOEK4KBb6v9EsBMFtI6V+OWCeP G9PMJjEWLcjf1DCBEECAIw41y9ZEZZpp/iGsBqzXSdt3JJF8TVsvW8eU/ZyvEswQtH0j Gw5Cx0AdU4e+rltJsbmHPjXFRk5rKilloewwCcI7BupkIpspq/TVVA/QjSQ16RZ2yKhK /b5C/WS9iqt628isUA6c1uHH3fYj2IZvX0l2nsgoQyL7v/r1uWolc+KqYgl/AC/AhY92 IrFMQq8sYmmNsXlZ30xcQ5c4JQ4GlQCLB/V2yXw1uNU2GKn8Dd+xhzol+4gqc4jQiJxf mIAg== 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:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=mE9DRDsHIsIHAbKbJFK2/CHjDpNdpunTcLE/Dg65eAI=; b=orzBSYkIUPSx8k6UXrBnHb3+er3M2EFq/TL/Vm326ujMDAKXUjTfMefYdUGNzkjrNI eocU1M33Pkzm1XgS6NZofaFs1TpZeLsEBU7yvAuoxz5im9F12WROa3XdgCPCQG47+UlQ YaJnIG+seU3NDbzDhK3BfyULFv50ieeNqEsVTm1IkLfuwPN3WNxFJE/2BIHL3mKbN4zh 7KVmL42UNifZI0G+SmT7pLw1NwniDdoLYKIu5u0Hie6yVylmF9/MVk/PzqS6Sc+ijNVF cz4yU6w7fEw8xo0adQbpWoP8DzQCQunVG8UiNm2+lq4CsqYA7KwEcV3Banhezx41iNyU YpjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@foxmail.com header.s=s201512 header.b=cXbmmcQ+; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=foxmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c17-20020a63d511000000b0038500c74446si19062640pgg.677.2022.03.29.12.45.41; Tue, 29 Mar 2022 12:45:55 -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; dkim=pass header.i=@foxmail.com header.s=s201512 header.b=cXbmmcQ+; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=foxmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239414AbiC2QNd (ORCPT + 99 others); Tue, 29 Mar 2022 12:13:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60720 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239392AbiC2QN3 (ORCPT ); Tue, 29 Mar 2022 12:13:29 -0400 X-Greylist: delayed 170632 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Tue, 29 Mar 2022 09:11:44 PDT Received: from out162-62-58-216.mail.qq.com (out162-62-58-216.mail.qq.com [162.62.58.216]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CAB0217ADAF for ; Tue, 29 Mar 2022 09:11:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1648570300; bh=mE9DRDsHIsIHAbKbJFK2/CHjDpNdpunTcLE/Dg65eAI=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=cXbmmcQ+c0qnHhF9v3lPJMwDk4yRXsmQFyINzr+IX+FE42HTskribPzu9HEnTkpCT mguTGGgqMjFNy/HWXUJl2CqFBiLO+47QUIBEQL+xG38/juqfLkCtmGjNNvxp/QRz8S jrQDROcDeTPdUE7435JkHas2Ir1qSADEvYWpM+q0= Received: from [192.168.31.6] ([120.245.132.52]) by newxmesmtplogicsvrszc11.qq.com (NewEsmtp) with SMTP id 28897A01; Wed, 30 Mar 2022 00:10:08 +0800 X-QQ-mid: xmsmtpt1648570208tm8np4p8u Message-ID: X-QQ-XMAILINFO: OYji31yNgomxdzawO0x/piNS6YFdtMMQ9FSm2rMyK0ZKdKsF7BqYhCbcqbwoqe zIDca7AZHfKpDI2L+27tL+KnvLyR9x6RzBCEIZ9B4BkS4ik46njjwKNB77HhZuCnWbCkUAC3kfuU 5zRur5hZB4BU8eSlXIT8XrWbuaDw1HXA1prNkvtjhVT8I0MRkRKzlePtdeMb61HC5mLlUWhzzp2+ EZkazy60AjWGEKJ6K3bmuiAOs1AA0XaMs2g7YgdimbIuvuKvybhQn6qXSpUQ+RleaQJFoqft692N h6mAAVIpGEAWyAej6EJKSqzt+MrWubXLWaS9F5j4S82FSY89gxKFGZLYstjUHz1zI6hglcNRE73p 22aT0X9P1QSwB4y90BxwIjWZU8Eq8otD7wr0cHJfGJU0PGOZbwT1S8PYhhnOEvVB2Z2VnQ7DH0bk 7ClNIi+Tcxk2nR/LJ0LZLRRQKWFjSSvcV441pEkF/nLnetAXA2f8Ex9ESiQHnZjhZMaHzWNEQbMB dCO8+6/Pw4u0X9FRqtX+2ol8DHvX/jReSSGr7dBAtICO5hna3OmGuflNrdsAuGxNMubnkhSJ0Rww Jai9IVA8zbE/iBNJV1vOxcVXjN7mXr8kvaMCP9ZuFHGRyvetQXqbMimDKIhZ9O6kfMgURpoRlc5X H+kfaggx7eOUabExe3RmT0R3reL1c3UyZ3DjeHihkTwMX9OlfKqr91nFgU4A3X3GUge10khC+jco wxZPSH8Xs1JqeJV01u4HSWKcyONaFG7XsEc93HDPOn7qTBvsvufxpDRhhMOZ/ryQ/Cvh9BYsm8yI 2pGoCzQDrI8/dBhoA5H6tqlEQ4IwsMm2zwpWM829u2kc5RaB8/AwpMB9I73dP3Gs+psCKeCE7sB5 yYzEw4mTBCK4JAlwLVrQs= X-OQ-MSGID: <0c20c29b-acc5-3bfa-4947-b7629c2a56ea@foxmail.com> Date: Wed, 30 Mar 2022 00:10:08 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH 0/3] ipmi: msghandler: check the users and msgs causing the system to block Content-Language: en-US To: minyard@acm.org Cc: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org References: <20220328013842.GN3457@minyard.net> <20220328154545.GP3457@minyard.net> From: chenchacha In-Reply-To: <20220328154545.GP3457@minyard.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=3.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FORGED_MUA_MOZILLA, FREEMAIL_FROM,HELO_DYNAMIC_IPADDR,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, RDNS_DYNAMIC,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: *** 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/3/28 23:45, Corey Minyard wrote: > On Mon, Mar 28, 2022 at 11:27:06PM +0800, chenchacha wrote: >> >>> Anyway, a better solution for the kernel side of things, I think, would >>> be to add limits on the number of users and the number of messages per >>> user. That's more inline with what other kernel things do. I know of >>> nothing else in the kernel that does what you are proposing. >> >> The precondition for add limits, is that people known that ipmi has too many >> users and messages cause problems, this patch is to let administrator known >> that. >> >> In addition, different machines have different limit, My server my block >> 700,000 messages and it's fine, and my NAS pc went to OOM when it probably >> blocked for 10,000 messages. So, to limit the number of users and messages, >> can wait until we have accumulated some online experience? > > I don't mean a limit on the total number of messages, but a limit on the > total number of oustanding messages, and a limit on the total number of > users. No user should have more than a handful of oustanding message, > and limiting the number of users to 20 or 30 should be more than enough > for any system. > > Having those limits in place would probably help you trace down your > problem, as you would hit the limits and it should report it at the > source of the problem. > > -corey Hi Corey: According to your suggestion, I have don some tests. After adding limits, event if the bmc hardware fails, the ipmi will not occupy a large memory in system. The modifications are in the next version of the patch. Thanks -- Chen Guanqiao