linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Pavel Roskin <proski@gnu.org>,
	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: Mon, 8 Nov 2010 16:33:44 -0500	[thread overview]
Message-ID: <20101108213343.GC2310@tuxdriver.com> (raw)
In-Reply-To: <AANLkTik80AuVEefHwccB81WPdT4UPfTSjQdG-3Yq17e7@mail.gmail.com>

On Fri, Nov 05, 2010 at 04:38:14PM -0700, Linus Torvalds wrote:
> On Fri, Nov 5, 2010 at 4:06 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > On 11/05/10 15:24, Linus Torvalds wrote:
> >>
> >> 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>
> 
> Goodie. Pavel, John - feel free to add my sign-off on that patch. Make
> up a relevant commit message. Ok?

In the queue...

commit 269e2d77b82d92d8dad543a2375e74372e9d773e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Nov 8 16:27:12 2010 -0500

    libipw: fix proc entry removal
    
    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.
    
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Tested-by: Randy Dunlap <randy.dunlap@oracle.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

Sorry for the delay -- I'm not a good traveler!
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2010-11-08 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimr3rW67HxgOUyReEW8dmmSsd4b7-Ns57mXzS1w@mail.gmail.com>
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
2010-11-05 23:38       ` Linus Torvalds
2010-11-08 21:33         ` John W. Linville [this message]

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=20101108213343.GC2310@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=randy.dunlap@oracle.com \
    --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 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).