netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 5/9] netfilter: xt_recent: allow changing ip_list_[ug]id at runtime
Date: Tue, 23 Mar 2010 16:10:15 +0100	[thread overview]
Message-ID: <4BA8D9D7.1080800@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1003231601250.21464@obet.zrqbmnf.qr>

Jan Engelhardt wrote:
> On Tuesday 2010-03-23 15:55, Patrick McHardy wrote:
>
>   
>>>>> -MODULE_PARM_DESC(ip_list_uid,"owner of /proc/net/xt_recent/* files");
>>>>> -MODULE_PARM_DESC(ip_list_gid,"owning group of /proc/net/xt_recent/* files");
>>>>> +MODULE_PARM_DESC(ip_list_uid, "default owner of /proc/net/xt_recent/* files");
>>>>> +MODULE_PARM_DESC(ip_list_gid, "default owning group of /proc/net/xt_recent/* files");
>>>>>       
>>>>>           
>>>> So what will be updating the permissions of the existing proc files?
>>>>         
>>> The administrator with the use of chmod/chown/chgrp.
>>>       
>> I'm not sure whether this will have the desired effect. I vaguely
>> recall that proc used to forget about permission changes. That might
>> have been fixed, but I was unable to find something in the
>> changelogs.
>>     
>
> I believe that the procfs alzheimer only applies to
> entries that are dynamically created during dentry lookup,
> e.g. all the things in /proc/1234. You will note that
> the inode numbers of these entries changes over time.
>
> This is not the case however for anything created with
> proc_create_data AFAICT.
>
> 16:04 linux:~ # ls -il /proc/1/stat
> 13294 -r--r--r-- 1 root root 0 Mar 23 16:04 /proc/1/stat
> 16:04 linux:~ # ls -il /proc/net/xt_recent/foo
> 4026532102 -rw-r--r-- 1 bin root 0 Mar 23 16:04
> /proc/net/xt_recent/foo
>
> # Drive out cached stuff
> 16:04 linux:~ # find / -xdev -type f -print0 | xargs -0 cat >/dev/null
> 16:04 linux:~ # echo 3 >/proc/sys/vm/drop_caches
>
> 16:04 linux:~ # ls -il /proc/1/stat
> 13399 -r--r--r-- 1 root root 0 Mar 23 16:04 /proc/1/stat
> 16:04 linux:~ # ls -il /proc/net/xt_recent/foo
> 4026532102 -rw-r--r-- 1 bin root 0 Mar 23 16:04 /proc/net/xt_recent/foo
>
> As you can see, /proc/X was reinstantiated, while xt_recent's data
> remained.
>   

Sounds good. In any case its not directly related to your patch, so this
seems fine.


  reply	other threads:[~2010-03-23 15:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 19:17 nf-next: cleanups, err reporting (rd.2) Jan Engelhardt
2010-03-22 19:17 ` [PATCH 1/9] netfilter: xtables: make use of caller family rather than target family Jan Engelhardt
2010-03-22 19:17 ` [PATCH 2/9] netfilter: xt extensions: use pr_<level> (2) Jan Engelhardt
2010-03-22 19:17 ` [PATCH 3/9] netfilter: xtables: make use of xt_request_find_target Jan Engelhardt
2010-03-23 14:24   ` Patrick McHardy
2010-03-23 14:27     ` Jan Engelhardt
2010-03-22 19:18 ` [PATCH 4/9] netfilter: xtables: consolidate code into xt_request_find_match Jan Engelhardt
2010-03-23 14:27   ` Patrick McHardy
2010-03-22 19:18 ` [PATCH 5/9] netfilter: xt_recent: allow changing ip_list_[ug]id at runtime Jan Engelhardt
2010-03-23 14:18   ` Patrick McHardy
2010-03-23 14:23     ` Jan Engelhardt
2010-03-23 14:55       ` Patrick McHardy
2010-03-23 15:06         ` Jan Engelhardt
2010-03-23 15:10           ` Patrick McHardy [this message]
2010-03-22 19:18 ` [PATCH 6/9] netfilter: xtables: slightly better error reporting (1/2) Jan Engelhardt
2010-03-22 19:18 ` [PATCH 7/9] netfilter: xtables: slightly better error reporting (2/2) Jan Engelhardt
2010-03-23 14:44   ` Patrick McHardy
2010-03-23 15:00     ` Jan Engelhardt
2010-03-23 15:02       ` Patrick McHardy
2010-03-22 19:18 ` [PATCH 8/9] netfilter: xtables: use only error codes for checkentry Jan Engelhardt
2010-03-22 19:18 ` [PATCH 9/9] netfilter: xtables: shorten up return clause Jan Engelhardt
2010-03-23 16:35 ` nf-next: cleanups, err reporting (rd.2) Jan Engelhardt
2010-03-25 12:48   ` Patrick McHardy

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=4BA8D9D7.1080800@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.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).