From owner-svn-src-all@freebsd.org Tue Dec 12 17:25:55 2017 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84699E9FB70; Tue, 12 Dec 2017 17:25:55 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 118F066DA3; Tue, 12 Dec 2017 17:25:54 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f45.google.com with SMTP id f20so24092905lfe.3; Tue, 12 Dec 2017 09:25:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UF0GyTHulBjHCz7PbpXmWLu7EFMfFxqQG4JEIyw4wxU=; b=CciA7knPIGM1paF2pzJowCBbTL5/rVIegfgTc6C7UDSe7y/QoOlPfMojjpREoiFyyo lCg2Vc2+jFTnevZwrarjEIPdTQaUe/npjj1hjslyQczR3xJZSloTTsZXfcMzxwlcm8zC reR1GXLzOpaQQAWQdmb3lTKQi9yeQJgY1LOzWFhOhp1NrkJvfN8PhE5G7FqLO8vxt1Jc 6DnVIhtqfOzLp7t1oR1GAy+Tw0PNOiQmUJ9xltIs6k7S8kTtkGhZGMOiX4td2lIDOkdw CNR62s5PNcZDRnAbi93tUhCMteqju/MwXc1LEU5vR/sRcuZdFVhNxjVgoJ3YvraO3UsW H8FA== X-Gm-Message-State: AKGB3mLG5L/L10o4XZWtTHBTDf7lkYUNh4PROXwaxhC0ERHkYkCiuX25 GIkB75v3Urywj+nAoLLxhu9je1oIIVc= X-Google-Smtp-Source: ACJfBosExh9UefQd9if/w7q+pQSjPuiiTxaJ9ossKi12qRzkL3MOxHBSmhFI3aH1r8YDAbuN8w7gCw== X-Received: by 10.46.68.11 with SMTP id r11mr2496928lja.1.1513099552128; Tue, 12 Dec 2017 09:25:52 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id 27sm3287379ljw.94.2017.12.12.09.25.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Dec 2017 09:25:51 -0800 (PST) Subject: Re: svn commit: r326758 - in head/sys/i386: conf include To: rgrimes@freebsd.org, Eugene Grosbein Cc: Don Lewis , Alexey Dokuchaev , Konstantin Belousov , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Conrad Meyer References: <201712121701.vBCH153d087153@pdx.rh.CN85.dnsmgr.net> From: Andriy Gapon Message-ID: <9484a39c-21f1-9174-11ce-54088c3f6099@FreeBSD.org> Date: Tue, 12 Dec 2017 19:25:49 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <201712121701.vBCH153d087153@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 17:25:55 -0000 On 12/12/2017 19:01, Rodney W. Grimes wrote: > We should probably start looking for those, something someone who is > offerring help but doesnt know what they might be good at, but can > read C code. They could be utililized t simply scan through the > code looking for this type of thing and bring it to the attention > of a area of expertise commiter. By the way, there are tools that can analyze binary code (e.g. a kernel binary or a module) and determine stack requirements of each function. I think that debug symbols might be required too. I am not sure if there are tools that can analyze stack requirements for possible call chains rather than individual functions. -- Andriy Gapon