Re: 2.6.35.4: sudo rmmod ahci @ 2.6.35.4 succeeds: filesystem access errors follow

Stefan Richter
2010-09-08T18:29:10Z

Pedro Francisco wrote:
> 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'

The usage count of a module is only there to ensure that function calls into
the module succeed. As long as some other part of the kernel has a pointer of
a function in the module, removal of the module needs to be prevented.

"rmmod ahci" on the other hand is something like pulling the SATA cable. Or
ejection of the controller from an ExpressCard slot. The driver shutdown
causes the controller device and thus its child devices (disk devices behind
the controller) to go away, and that's it. You can do also
# echo $DEVICE_ID > /sys/module/ahci/drivers/pci\:ahci/unbind
which tells the driver to let go of the controller.
--
Stefan Richter
-=====-==-=- =--= -=---