Skip to contentSkip to conversation

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

DISCUSSION Pedro Francisco 3 participants 5 messages Sep 7, 2010 – Sep 8, 2010

lore
Share & tools
lore
#0 lore raw

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?
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.

Signature · 1 line
Pedro
#1 lore raw
Quoted 5 lines · El Tue, 7 Sep 2010 18:34:27 +0100 Pedro Francisco <[email protected]>…

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.

Quoted 8 lines

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 / »

Quoted 4 lines

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.

#2 lore raw
Quoted 11 lines · On Tuesday 07 September 2010 19:21:43 Alejandro Riveira Fernández wrote:

El Tue, 7 Sep 2010 18:34:27 +0100

Quoted 8 lines · Pedro Francisco

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]:

Quoted 8 lines
Quoted 5 lines

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'

Quoted 5 lines
Quoted 5 lines

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.

Signature · 1 line
Pedro
#3 lore raw
Quoted 17 lines · Pedro Francisco
Quoted 16 lines · On Tuesday 07 September 2010 19:21:43 Alejandro Riveira Fernández wrote:

El Tue, 7 Sep 2010 18:34:27 +0100

Quoted 13 lines · Pedro Francisco

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?

Quoted 6 lines
Quoted 2 lines

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.
Signature · 3 lines
Stefan Richter
-=====-==-=- =--= -=---
http://arcgraph.de/sr/
#4 lore raw
Quoted 10 lines · On Wednesday 08 September 2010 19:28:57 Stefan Richter wrote:
Quoted 3 lines · Pedro Francisco

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.

Quoted 6 lines

"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.

Hum ok... Still I find it weird since on 2.6.32 I've, after `lsmod | grep -i ahci':
ahci 32200 4
and on 2.6.35.4:
ahci 32200 0

Why the change of behaviour? Is it because of the split of libahci from ahci ?

Signature · 1 line
Pedro