From: Ravi Prakash Putchala <praks.putchala@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: fs.quota.warnings sysctl parameter usage
Date: Thu, 16 May 2019 19:59:41 +0530 [thread overview]
Message-ID: <CABRTiai=KAWn_a5aWvPp9kCn757hm5HXvkN5kxMq+8nUBtu4FA@mail.gmail.com> (raw)
In-Reply-To: <20190515112636.GA11749@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 1517 bytes --]
Thank you. This helps a lot. I will check it out.
On Wed, May 15, 2019 at 5:04 PM Greg KH <greg@kroah.com> wrote:
> 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 <greg@kroah.com> 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
>
[-- Attachment #1.2: Type: text/html, Size: 2071 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-05-16 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 7:44 fs.quota.warnings sysctl parameter usage Ravi Prakash Putchala
2019-05-15 8:16 ` Greg KH
2019-05-15 10:11 ` Ravi Prakash Putchala
2019-05-15 11:26 ` Greg KH
2019-05-16 14:29 ` Ravi Prakash Putchala [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABRTiai=KAWn_a5aWvPp9kCn757hm5HXvkN5kxMq+8nUBtu4FA@mail.gmail.com' \
--to=praks.putchala@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).