public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel@vger.kernel.org, Nick Piggin <npiggin@kernel.dk>,
	Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Howells <dhowells@redhat.com>,
	"Serge E. Hallyn" <serge.hallyn@canonical.com>,
	Daniel Lezcano <daniel.lezcano@free.fr>,
	Jiri Slaby <jslaby@suse.cz>, Greg Kroah-Hartman <gregkh@suse.de>,
	James Morris <jmorris@namei.org>
Subject: Re: [PATCH] sysctl: add support for poll()
Date: Thu, 02 Jun 2011 06:56:27 -0700	[thread overview]
Message-ID: <m1hb88e3qs.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <BANLkTik72cU_R5k9NLnqN_FNkm-y5Fk0nQ@mail.gmail.com> (Lucas De Marchi's message of "Thu, 2 Jun 2011 10:02:50 -0300")

Lucas De Marchi <lucas.demarchi@profusion.mobi> writes:

> On Thu, Jun 2, 2011 at 9:43 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>> The alternative is to have a process constantly polling and reading
>>> the file, which is nothing we even want to think about in 2011.
>>
>> Or to manage it properly.
>
> What if the user decides do invoke sethostname syscall "by hand"?
> Hostname would change beneath any other process that is trying to
> manage it properly. What this patch does is to notify that process
> that something happened.
>
>
>>> It's just another special case to bring us out of the UNIX stone age
>>> of doing things. :)
>>
>> Unfortunately not. It's a misguided attempt to follow stone age Unix 'one
>> short name' policy. Forget utsname node names, they are a historical
>> quirk of UUCP and friends and on many OS platforms will be limited to 15
>> chars !
>>
>> As to poll in general I can see some of the other proc files being
>> more relevant, eg for process monitoring tools being able to poll
>> in /proc/<pid> and some of the proc/sys and sysctl data that does change
>> meaningfully. Utsname however is not one of those things.
>>
>
> With this patch in, if anyone wants to manage a file under /proc/sys
> there's really a small amount of code to write. He only has to define
> the new poll struct for that file.

The support currently appears cumbersome to add, and it adds what appear
to be unnecessary wake ups (say when the hostname in another uts
namespace changes).

There is no explanation at all of why you care about the nis domainname.

Since there does not appear to be a specific problem that this problem
is being aimed at, since the code just looks like extra maintenance and
since the code needed to support this appears to be unnecessarily
cumbersome I am going to nack the patch for now.

Nacked-by: "Eric W. Biederman" <ebiederm@xmission.com>

If the goal here is just to fix the general case then we probably
want to get inotify going on proc files instead of poll.  Either
that or we want pollable files to appear as something besides files
so that it is clear to their users that poll will work.

Eric

  parent reply	other threads:[~2011-06-02 13:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 12:14 [PATCH] sysctl: add support for poll() Lucas De Marchi
2011-06-02  2:51 ` Lucas De Marchi
2011-06-02  3:31   ` Eric W. Biederman
2011-06-02 12:06     ` Kay Sievers
2011-06-02 12:43       ` Alan Cox
2011-06-02 13:01         ` Kay Sievers
2011-06-02 13:02         ` Lucas De Marchi
2011-06-02 13:12           ` Alan Cox
2011-06-02 13:24             ` Kay Sievers
2011-06-02 13:56           ` Eric W. Biederman [this message]
2011-06-02 17:32             ` Kay Sievers
2011-06-08 22:17               ` Andrew Morton
2011-06-09 13:16                 ` Kay Sievers
2011-06-13 16:05                   ` Kay Sievers
2011-06-14  3:53                     ` Lucas De Marchi
2011-06-14  4:17                     ` NeilBrown
2011-07-26  2:17                     ` Lucas De Marchi
2011-08-02 22:53                       ` Kay Sievers
2011-08-02 23:16                         ` Greg KH
2011-08-03  1:12                           ` Lucas De Marchi
2011-08-03  9:40                             ` Eric W. Biederman
2011-08-03 13:17                               ` Lucas De Marchi
2011-08-03 18:08                                 ` Eric W. Biederman
2011-08-03 18:45                                   ` Lucas De Marchi
2011-08-04 18:57                                     ` Lucas De Marchi
2011-08-23 17:57                                       ` Greg KH
2011-08-26 21:06                                       ` Andrew Morton
2011-06-12 15:34               ` Eric W. Biederman
2011-06-13 14:28                 ` Kay Sievers
2011-06-02 14:16         ` Eric W. Biederman

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=m1hb88e3qs.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=daniel.lezcano@free.fr \
    --cc=dhowells@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hch@lst.de \
    --cc=jmorris@namei.org \
    --cc=jslaby@suse.cz \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=npiggin@kernel.dk \
    --cc=serge.hallyn@canonical.com \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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