linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	adaplas@gmail.com, linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Fix /proc/fb oops after module removal
Date: Sun, 13 Apr 2008 08:42:47 -0700	[thread overview]
Message-ID: <20080413084247.245d4711@laptopd505.fenrus.org> (raw)
In-Reply-To: <20080412152006.02134bf3.akpm@linux-foundation.org>

On Sat, 12 Apr 2008 15:20:06 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sun, 13 Apr 2008 01:10:29 +0400 Alexey Dobriyan
> <adobriyan@gmail.com> wrote:
> 
> > /proc/fb is not removed during rmmod.
> > 
> > Steps to reproduce:
> > 
> > 	modprobe fb
> > 	rmmod fb
> > 	ls /proc
> > 

> 
> hm, that's the sort of thing which one would expect people to notice
> fairly soon after we added the bug.  Yet it appears that the bug is
> present in at least 2.6.20 and probably earlier.

rmmod is generally a rare operation... esp for something like a framebuffer

wonder if we need a scripted action that loads all modules and then tries to 
unload the ones it can

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

      reply	other threads:[~2008-04-13 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080412211029.GG9151@martell.zuzino.mipt.ru>
2008-04-12 22:20 ` [PATCH] Fix /proc/fb oops after module removal Andrew Morton
2008-04-13 15:42   ` Arjan van de Ven [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=20080413084247.245d4711@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=adaplas@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).