All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Francisco <pedrogfrancisco@gmail.com>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35.4: sudo rmmod ahci @ 2.6.35.4 succeeds: filesystem access errors follow
Date: Tue, 7 Sep 2010 22:47:18 +0100	[thread overview]
Message-ID: <201009072247.18438.pedrogfrancisco@gmail.com> (raw)
In-Reply-To: <20100907202143.02cf60ec@varda>

On Tuesday 07 September 2010 19:21:43 Alejandro Riveira Fernández wrote:
> El Tue, 7 Sep 2010 18:34:27 +0100
> 
> Pedro Francisco <pedrogfrancisco@gmail.com> escribió:
> > sudo rmmod ahci @ 2.6.35.4 succeeds: filesystem access errors follow.
> > 
> > Now what I'm surprised is not the filesystem errors but me being allowed
> > to remove the module without using the '-f' option.
> > 
> > Do note, lsmod |grep ahci reports something like [this is adapted from a
> > 2.6.32 kernel]:
> > 
> > ahci                   32200  0
> > 
> > so it isn't at all surprising I'm being allowed to remove a seemingly
> > unused module. So....
> > a) is this supposed to happen?
> 
>  Yes afaics. root can do many stupid things if (s)he wants
>  including « rm -rf --no-preserve-root / »

That makes no sense. That's what the force option "-f" is for. It's my opinion 
the usage count for ahci on `lsmod' should be 1 and not 0. Whoever still wants 
to remove it can use the `rmmod -f ahci'


> 
> > b) do you need any more info?
> > 
> > P.S.: CC'ing me will probably ensure I'll reply faster but not explicitly
> > needed since I'm subscribed.


-- 
Pedro

  reply	other threads:[~2010-09-07 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 17:34 2.6.35.4: sudo rmmod ahci @ 2.6.35.4 succeeds: filesystem access errors follow Pedro Francisco
2010-09-07 18:21 ` Alejandro Riveira Fernández
2010-09-07 21:47   ` Pedro Francisco [this message]
2010-09-08 18:28     ` Stefan Richter
2010-09-08 19:49       ` Pedro Francisco

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=201009072247.18438.pedrogfrancisco@gmail.com \
    --to=pedrogfrancisco@gmail.com \
    --cc=ariveira@gmail.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.