All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysfs-related oops during module unload (2.6.16-rc2)
Date: Mon, 20 Feb 2006 23:50:39 -0600	[thread overview]
Message-ID: <20060221055039.GG3293@localhost.localdomain> (raw)
In-Reply-To: <20060219005716.GA5800@kroah.com>

Greg KH wrote:
> On Sat, Feb 18, 2006 at 06:47:51PM -0600, Nathan Lynch wrote:
> > Sorry for the delay.
> > 
> > Tested against 2.6.16-rc4-ish, and it seems to do the right thing --
> > modprobe -r says the module is busy while the refcnt attribute is
> > open.  The module is allowed to unload once the file is closed.
> 
> Great, thanks for trying it out and letting me know.

Sure -- do you plan to push this for 2.6.16?

The reason I ask is that the refcnt attribute is world-readable, so a
malicious or silly user can keep the file open until an unwitting
superuser unloads a module...

Far-fetched, I suppose, but I just wanted to make this scenario clear.


Nathan

  reply	other threads:[~2006-02-21  5:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 22:03 sysfs-related oops during module unload (2.6.16-rc2) Nathan Lynch
2006-02-11 22:45 ` Greg KH
2006-02-12  5:27   ` Nathan Lynch
2006-02-12  5:38     ` Greg KH
2006-02-16 21:50       ` Greg KH
     [not found]         ` <200602162253.45621.dtor_core@ameritech.net>
2006-02-18  0:36           ` Greg KH
2006-02-19  0:47         ` Nathan Lynch
2006-02-19  0:57           ` Greg KH
2006-02-21  5:50             ` Nathan Lynch [this message]
2006-02-21  6:12               ` Greg KH

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=20060221055039.GG3293@localhost.localdomain \
    --to=ntl@pobox.com \
    --cc=greg@kroah.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 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.