mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] proc: Make the generation of the self symlink table driven.
Date: Thu, 7 Sep 2006 10:15:12 -0700	[thread overview]
Message-ID: <20060907101512.3e3a9604.akpm@osdl.org> (raw)
In-Reply-To: <m1odttx8uz.fsf@ebiederm.dsl.xmission.com>

On Wed, 06 Sep 2006 10:23:00 -0600
ebiederm@xmission.com (Eric W. Biederman) wrote:

> 
> This patch generalizes the concept of files in /proc that are
> related to processes but live in the root directory of /proc
> 
> Ideally this would reuse infrastructure from the rest of the
> process specific parts of proc but unfortunately
> security_task_to_inode must not be called on files that
> are not strictly per process.  security_task_to_inode
> really needs to be reexamined as the security label can
> change in important places that we are not currently
> catching, but I'm not certain that simplifies this problem.
> 
> By at least matching the structure of the rest of proc
> we get more idiom reuse and it becomes easier to spot problems
> in the way things are put together.
> 
> Later things like /proc/mounts are likely to be moved into
> proc_base as well.  If union mounts are ever supported
> we may be able to make /proc a union mount, and properly
> split it into 2 filesystems.
> 
> ..
>
>  /*
> + * proc base
> + *
> + * These are the directory entries in the root directory of /proc
> + * that properly belong to the /proc filesystem, as they describe
> + * describe something that is process related.
> + */
> +static struct pid_entry proc_base_stuff[] = {
> +	NOD(PROC_TGID_INO, 	"self", S_IFLNK|S_IRWXUGO,
> +		&proc_self_inode_operations, NULL, {}),
> +	{}
> +};

We could save a bunch of bytes here.

> +	/* Lookup the directory entry */
> +	for (p = proc_base_stuff; p->name; p++) {

By using ARRAY_SIZE here.

> +	for (; nr < (ARRAY_SIZE(proc_base_stuff) - 1); filp->f_pos++, nr++) {

like that does.



  parent reply	other threads:[~2006-09-07 17:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 16:23 Eric W. Biederman
2006-09-06 16:24 ` [PATCH 2/5] proc: Factor out an instantiate method from every lookup method Eric W. Biederman
2006-09-06 16:27   ` [PATCH 3/5] proc: Remove the hard coded inode numbers Eric W. Biederman
2006-09-06 16:28     ` [PATCH 4/5] proc: Merge proc_tid_attr and proc_tgid_attr Eric W. Biederman
2006-09-06 16:31       ` [PATCH 5/5] proc: Use pid_task instead of open coding it Eric W. Biederman
2006-09-07 17:22     ` [PATCH 3/5] proc: Remove the hard coded inode numbers Andrew Morton
2006-09-07 17:55       ` Eric W. Biederman
2006-09-07 18:06         ` Andrew Morton
2006-09-07 18:37           ` Eric W. Biederman
2006-09-07 17:18   ` [PATCH 2/5] proc: Factor out an instantiate method from every lookup method Andrew Morton
2006-09-07 18:08     ` Eric W. Biederman
2006-09-07 17:15 ` Andrew Morton [this message]
2006-09-07 18:04   ` [PATCH 1/5] proc: Make the generation of the self symlink table driven Eric W. Biederman
2006-09-08  7:07   ` Jan Engelhardt
2006-09-08 11:04     ` Eric W. Biederman
2006-09-08 13:08       ` Jan Engelhardt
2006-09-08 13:27         ` Eric W. Biederman
2006-09-08 16:55           ` Jan Engelhardt
2006-09-09  2:34             ` 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=20060907101512.3e3a9604.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@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

Powered by JetHome