From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pavel Roskin <proski@gnu.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc1 (libipw remove_proc_entry warning)
Date: Fri, 05 Nov 2010 16:06:44 -0700 [thread overview]
Message-ID: <4CD48E04.2050709@oracle.com> (raw)
In-Reply-To: <AANLkTimnHFHJq13xpJ0ZgLmpd+cHmHH5sQ4HWtL_MrMT@mail.gmail.com>
On 11/05/10 15:24, Linus Torvalds wrote:
> This bug seems to be due to commit 27ae60f8f7aac ("ipw2x00: replace
> "ieee80211" with "libipw" where appropriate"), where Pavel did this:
>
> - libipw_proc = proc_mkdir(DRV_NAME, init_net.proc_net);
> + libipw_proc = proc_mkdir("ieee80211", init_net.proc_net);
>
> but then the cleanup was kept as
>
> remove_proc_entry(DRV_NAME, init_net.proc_net);
>
> in both places (both in the failure case and in the unload case). The
> error string is also total crap, and says
>
> "Unable to create " DRV_NAME " proc directory\n");
>
> Even though it doesn't actually create a proc directory named DRV_NAME at all.
>
> So that patch looks like total and utter crap to me. The commit message says
>
> "Keep /proc/net/ieee80211 under the original name to avoid breaking user
> interface."
>
> but the thing is, it really didn't fix anything but that one create
> thing. It needs to fix all the other cases too.
>
> Totally UNTESTED patch attached. It may or may not compile. And maybe
> it doesn't catch all cases, but it should catch the obvious ones.
That works for me.
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>
thanks,
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-05 23:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 12:07 Linux 2.6.37-rc1 Linus Torvalds
2010-11-01 15:37 ` Thomas Gleixner
2010-11-01 15:47 ` Nick Bowler
2010-11-01 15:52 ` Ryusuke Konishi
2010-11-01 16:07 ` Linus Torvalds
2010-11-02 18:51 ` Linux 2.6.37-rc1 (acpi_video) Randy Dunlap
2010-11-03 21:08 ` Linux 2.6.37-rc1 (cciss: remove_proc_entry warning) Randy Dunlap
2010-11-03 21:15 ` Linux 2.6.37-rc1 (pcrypt fault) Randy Dunlap
2010-11-03 21:15 ` Randy Dunlap
2010-11-10 11:21 ` Steffen Klassert
2010-11-10 18:11 ` Randy Dunlap
2010-11-03 21:21 ` Linux 2.6.37-rc1 (net/sched: cls_cgroup) Randy Dunlap
2010-11-03 21:21 ` Randy Dunlap
2010-11-03 22:01 ` Eric Dumazet
2010-11-03 22:01 ` Eric Dumazet
2010-11-03 22:19 ` Li Zefan
2010-11-03 22:19 ` Li Zefan
2010-11-03 22:31 ` Li Zefan
2010-11-03 22:31 ` Li Zefan
2010-11-03 23:31 ` Herbert Xu
2010-11-03 23:31 ` Herbert Xu
2010-11-04 1:46 ` Li Zefan
2010-11-04 1:46 ` Li Zefan
2010-11-04 1:56 ` David Miller
2010-11-04 1:56 ` David Miller
2010-11-04 15:56 ` Randy Dunlap
2010-11-03 23:16 ` Linux 2.6.37-rc1 (floppy module load: no device found) Randy Dunlap
2010-11-05 22:10 ` Linus Torvalds
2010-11-05 22:12 ` David Miller
2010-11-05 23:03 ` Randy Dunlap
2010-11-05 23:36 ` Linus Torvalds
2010-11-06 0:33 ` Randy Dunlap
2010-11-06 12:16 ` Vivek Goyal
2010-11-06 14:52 ` Linus Torvalds
2010-11-03 23:18 ` Linux 2.6.37-rc1 (libipw remove_proc_entry warning) Randy Dunlap
2010-11-05 22:24 ` Linus Torvalds
2010-11-05 23:06 ` Randy Dunlap [this message]
2010-11-05 23:38 ` Linus Torvalds
2010-11-08 21:33 ` John W. Linville
2010-11-03 23:20 ` Linux 2.6.37-rc1 (scsi_debug: list corruption) Randy Dunlap
2010-11-03 23:20 ` Randy Dunlap
2010-11-04 2:25 ` Xiaotian Feng
2010-11-04 2:25 ` Xiaotian Feng
2010-11-04 16:12 ` Randy Dunlap
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=4CD48E04.2050709@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.