Date: Sun, 31 Aug 2003 14:40:33 -0700
From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: create_proc_entry and !CONFIG_PROC_FS
Message-Id: <20030831144033.6f9d8708.akpm@osdl.org>
In-Reply-To: <20030831150632.GU7038@fs.tum.de>
References: <20030831150632.GU7038@fs.tum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1458
Lines: 41

Adrian Bunk <bunk@fs.tum.de> wrote:
>
> Hi,
> 
> I've observed a possible problem with create_proc_entry and 
> !CONFIG_PROC_FS.
> 
> If !CONFIG_PROC_FS include/linux/proc_fs.h includes a dummy 
> create_proc_entry that simply returns NULL.
> 
> Unfortunately, many callers of this function do things like e.g.
> 
> static int __init br2684_init(void)
> {
>         struct proc_dir_entry *p;
>         if ((p = create_proc_entry("br2684", 0, atm_proc_root)) == NULL)
>                 return -ENOMEM;
>         p->proc_fops = &br2684_proc_operations;
>         br2684_ioctl_set(br2684_ioctl);
>         return 0;
> }
> 
> 
> IOW, the dummy create_proc_entry fixes the compilation but the init 
> function always returns -ENOMEM if !CONFIG_PROC_FS.
> 
> Is there any better solution than removing the dummy create_proc_entry 
> and #ifdef'ing all places where it's used?

The normal fix would be to sprinkle ifdefs throughout the driver itself.

You need to lok at the driver and ask yourself "is anyone ever going to want
to use this in a no-procfs system".  Probably, the answer is always "no". 
In which case appropriate fixes would be to ignore the problem, or disable
the driver in config if !CONFIG_PROC_FS.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/