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=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham 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 ABD5CC04E53 for ; Wed, 15 May 2019 11:34:54 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 601C82053B for ; Wed, 15 May 2019 11:34:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="zvzlVMst"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="LBtmxKoK" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 601C82053B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1hQsB0-0001DS-3k; Wed, 15 May 2019 07:34:26 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1hQsAy-0001DL-Dp for kernelnewbies@kernelnewbies.org; Wed, 15 May 2019 07:34:24 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CEB8C24E00; Wed, 15 May 2019 07:34:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 15 May 2019 07:34:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=3WYQBtiHEa9X/nQFAhjHxG688en sKDmBJzx5h44py90=; b=zvzlVMstKXNkVBh+Lx2cXXn03BLl9EpxvayMNiak7jW QFxrvrmbtH95wpIl9vwQabkNSszWL0vcU2JClf5SKjiA+qgBgIX1ONxUnYn+fMod X3wWahuV01+Wv3OH4fLZzlMLxhFxJBnh/7BOfU70ASA0jNxij+qVFPI+0btANkS8 OVp/dzKGngb6lkNIhoVHyclEVevvuBXKLtFV+JqDBKcPyGirK71cHGdOUSdCNdc6 KxUkXaPhd8KxKpEMBAwY+mruUAX5VVWCilktHDehxMsjEL/c8JPnwICvFAowpg+r Cf5wTg3GrAVi5VIwgOd8EuVQ7BApM6rSydt7yLJbe8g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=3WYQBt iHEa9X/nQFAhjHxG688ensKDmBJzx5h44py90=; b=LBtmxKoKNPDyp4RxFcaE+r 18PazO4uQGO/L4jp0SEjptUk/m78d7fXMzSyXOhHLerd5MrZlnfKpRU9E7QigiB7 ets1pqOZBvsxGYhANKNlOgcvjLHoltMAHzp+H//+Hv0LSQUd1nr/qYqm0SWScZi3 KjkDAKgWsDtn7sb+DREBqUyjQ9EcssZ9vSYTjxIi+c0Seofe4tpAjyasDVsIFPK4 HPgEy/nGiksMDG6ED7+5AF/35RP9drweaypOzxFZSlWfkck4PkfHsBABr09GKzj5 kKRAf8RxSEVGaGGTi6eLPLMvBU7t8L+G1GC1nm17iqutEjBE9xxwzJbFQgB3rH0w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrleekgdegfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucfkphepkeefrdekiedrkeelrddutd ejnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomhenucev lhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 013C880059; Wed, 15 May 2019 07:34:21 -0400 (EDT) Date: Wed, 15 May 2019 13:26:36 +0200 From: Greg KH To: Ravi Prakash Putchala Subject: Re: fs.quota.warnings sysctl parameter usage Message-ID: <20190515112636.GA11749@kroah.com> References: <20190515081656.GB22750@kroah.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Wed, May 15, 2019 at 03:41:30PM +0530, Ravi Prakash Putchala wrote: > On Wed, May 15, 2019 at 1:46 PM Greg KH wrote: > > > On Wed, May 15, 2019 at 01:14:24PM +0530, Ravi Prakash Putchala wrote: > > > Hi, > > > > > > I am exploring fs sysctl parameters and unable to find the reference to > > > fs.quota.warnings parameter in the kernel source code. I tried searching > > > with fs.quota.warnings (ignoring case) and also sysctl_fs_quota_warnings. > > > > > > Could anyone please point me to the place in the kernel source where this > > > parameter is used? > > > > Look at the flag_print_warnings variable in fs/quota/dquot.c > > > > Thank you. But how do I associate it with fs.quota.warnings? Asking because > this would be useful for me to associate other sysctl parameters in > future. Step back a minute and think about how you create a sysctl entry. It's with a call to register_sysctl_table(), right? And what is the parameter of that function? It takes a table that describes the sysctl directory structure. And from that you can see the different quota sysctl entries and variables. Look at the sys_table and fs_table structures for that information, understand how they work and then you will be able to find any sysctl entry in the kernel source quite easily. hope this helps, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies